Re: Refreshing complete page from a header component
Re: Refreshing complete page from a header component
- Subject: Re: Refreshing complete page from a header component
- From: Steven Mark McCraw <email@hidden>
- Date: Fri, 29 Jun 2007 09:39:57 -0400
Can anyone comment on the benefits of returning context().page() vs.
returning null for an action method? Returning context().page()
seems to not work when using Wonder Ajax components, so I always
return null there. Someone who worked at Apple once told me that
returning context().page() was WAY more efficient. I took them at
their word and started using it everywhere, but it's come to be one
of those things that I kind of doubt makes that big of a difference.
Does anyone know what the difference actually is, and why one might
be better than the other?
Mark
On Jun 29, 2007, at 9:17 AM, Paul Lynch wrote:
On 29 Jun 2007, at 12:31, Johan Henselmans wrote:
I must be missing something: I have a header component, which
contains the menubar, and sets the default language, by calling
session.setlanguages() via a WOHyperlink. After that I want to
return the current page. But a "return this" from within the
Header WOComponent will only return the header. Any idea how to
get the current page returned from within the header component?
This is the structure:
WOComponent->Page
WOComponent->Header
rest....
WOComponent->Footer
Try:
return context().page();
Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40bluecollarsoftware.com
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