• 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: Refreshing complete page from a header component
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Refreshing complete page from a header component


  • Subject: Re: Refreshing complete page from a header component
  • From: Paul Lynch <email@hidden>
  • Date: Fri, 29 Jun 2007 14:50:26 +0100

Returning null is quite interesting, as it seems to return (so I was once told) the last component used to generate a page - like possibly an email page component. I haven't bothered to personally verify this, but plenty of people have reported similar situations.

I take the approach of least code - for a simple app, I return null, but if the situation warrants it, I might regenerate a new page with pageWithName(), or return context().page(); whichever results in what I think is the clearest code.

context().page() returns a specific component, just like pageWithName () does, but without the overhead of creating and initialising it; when you return null, WO has to work out which page you might have meant. The performance difference doesn't have to be large, although I have been told the same as you.

Paul

On 29 Jun 2007, at 14:39, Steven Mark McCraw wrote:

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();

_______________________________________________ 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
References: 
 >Refreshing complete page from a header component (From: Johan Henselmans <email@hidden>)
 >Re: Refreshing complete page from a header component (From: Paul Lynch <email@hidden>)
 >Re: Refreshing complete page from a header component (From: Steven Mark McCraw <email@hidden>)

  • Prev by Date: Re: Refreshing complete page from a header component
  • Next by Date: Re: Pretty printing?
  • Previous by thread: Re: Refreshing complete page from a header component
  • Next by thread: Re: Refreshing complete page from a header component
  • Index(es):
    • Date
    • Thread