• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AjaxObserveField bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AjaxObserveField bug?


  • Subject: Re: AjaxObserveField bug?
  • From: email@hidden
  • Date: Sat, 19 Dec 2009 17:23:37 -0500

Shouldn't matter... Can you put together a small example app that demonstrates it.

Sent from my iPhone

On Dec 19, 2009, at 3:33 PM, "Jerald Dawson"<email@hidden> wrote:

To follow up on this email, I changed the subclass to ERXComponent and it works fine now. I'm guessing I just overlooked something in the Ajax framework docs that say they only work if the parent component subclass ERXComponent?

On Dec 19, 2009, at 2:21 PM, Jerald Dawson wrote:

Oh dang it. I hate it when this happens. I tried coming up with a little contrived example to send to show you the issue and its working fine in the example. After going back and looking at everything, the only difference i can find is that my example component subclasses ERXComponent whereas my project component subclasses a utility component that I wrote a while back that takes care of ssl and authentication and whatnot and eventually extends WOComponent (ERXComponent is not in the hierarchy). Could this be an issue?

-j

On Dec 19, 2009, at 11:20 AM, Mike Schrag wrote:

"you're doing it wrong"

please paste examples of both ...

On Dec 19, 2009, at 12:18 PM, Jerald Dawson wrote:

Hey all

I recently fell in love with inline bindings and so decided to use them on a new project I was starting. Everything was going along smokingly until I tried to use an AjaxObserveField component. When I use normal wod file bindings, the AjaxObserveField works as expected. If I try to use the ognl inline bindings, it does not work. Instead of binding to the correct observeFieldId, it creates a new div with a random id and binds to that. I can use inline bindings for everything else but I'm forced to use to the wod file to define the AjaxObserveField bindings. I'm using the newest wonder (just upgraded yesterday to the latest from the website). Its not a huge show stopper since I did find a workaround but I was hoping to relegate the wod file to the dustbin of history.

Jerald Dawson _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: AjaxObserveField bug?
      • From: Jerald Dawson <email@hidden>
References: 
 >AjaxObserveField bug? (From: Jerald Dawson <email@hidden>)
 >Re: AjaxObserveField bug? (From: Mike Schrag <email@hidden>)
 >Re: AjaxObserveField bug? (From: Jerald Dawson <email@hidden>)
 >Re: AjaxObserveField bug? (From: Jerald Dawson <email@hidden>)

  • Prev by Date: Re: AjaxObserveField bug?
  • Next by Date: Re: AjaxObserveField bug?
  • Previous by thread: Re: AjaxObserveField bug?
  • Next by thread: Re: AjaxObserveField bug?
  • Index(es):
    • Date
    • Thread