| what about wrapping it in an AjaxUpdateContainer? or rather an observeField that deliberately updates the form.
Just an idea.
On Aug 25, 2013, at 3:25 PM, "Josef M. Burzler" < email@hidden> wrote: A Workaround for this kind of problem is: evaluate the condition used in the binding within the appendToResponse-method ) of the component, before calling super.appendToResponse, store the result into a variable and use this variable for the binding of the conditional.
Am 24.08.2013 um 16:41 schrieb Laurence Mills-Gahl < email@hidden>: Ahhhhh…. This sounds like a likely situation. The component is a quick search box that requires a facility to be selected to limit the search so the first time through a message is displayed about making the selection… hmm…
On Aug 23, 2013, at 7:14 PM, Ramsey Gurley < email@hidden> wrote: This can happen when the hyperlink is after a conditional and the conditional evaluates differently on the second request, thus changing the hyperlink's element ID.
request - serve page condition = true elementID -> 0.0.0.5 response request - click link condition = false elementID -> 0.0.0.1 response - oops, no such element 0.0.0.5. invokeAction comes up empty handed On Aug 23, 2013, at 3:51 PM, Laurence Mills-Gahl wrote: Hello,
I have a WOHyperlink with an action bound but the action doesn't get called. I set a breakpoint in the method and run it in debug mode, but it never breaks. I must be spending too much time looking at this to see (what must be) an obvious problem, but I cannot see what the problem is. This is a basic WOHyperlink with an action.
Anybody have an ideas where I can look for causes?
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
|