Re: invokeAction Question
Re: invokeAction Question
- Subject: Re: invokeAction Question
- From: Andrew Lindesay <email@hidden>
- Date: Wed, 7 Feb 2007 12:10:00 +1300
Hello Chuck;
In general my apps are wrapped in a switch component so many
invokeActions are finally returning 'null' to get back to the same
"page-wrapper",
return context().page() is probably the better choice.
For various reasons, returning null is better for my architecture.
I think you are missing an important check here. You are assuming
that the action is for this component, but it might not be. if
(context.senderID().equals(context.elementID()( {
I know this works well for "href actions" as it is what I usually do,
but I imagine that in a WOForm, this is not workable. The senderId
for a "multipleSubmit" WOForm I would assume is the WOForm's
elementId which would not fire the action that is bound to the
WOSubmitButton if I used the logic above. I assume that the
WOSubmitButton must be doing something akin to what I have done in my
component.
This mechanism is working 100% except that I am somehow loosing
the returned value from this method further up the component
heirachy.
If you have code like the above elsewhere, that may explain what
you are seeing.
No, in this case, there are no other component of my making doing
similar stuff on this page and in any case I don't imagine this could
be a problem anyway.
Can anybody else confirm that if you return non-null from an
invokeAction that the _correct_ response from the parental component
is to discontinue calling latter invokeAction methods on the
component tree and instead return the non-null value?
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
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