Salut Stephane, in case it does not matter that a particular instance of a Page is returned (and thanks to @Persist and @ApplicationState this seldomly is), I use to return the class Object of the page (e.g. MyPage.class) rather than "this". If I got the manual right, this leaves the decision, which particular instance to choose from the page pool, to tapestry´s page pooling mechanism. Which I trust more to do it efficiently than my own code. As far as I understand this makes your application more scalable.
Regards, nillehammer ----- original Nachricht -------- Betreff: Re: T5 : Event bubbling Gesendet: Do, 10. Apr 2008 Von: Stephane Decleire<[EMAIL PROTECTED]> > Thanks Armand. > Returning 'this' works great ! > > Stephane > > Francois Armand a écrit : > > Stephane Decleire wrote: > >> correct behavior of event bubbling in T5 (i mean handlers which > >> returns null values do not catch the event) ? > >> If yes, what is the solution for an handler to both catch the event > >> and show the same page to the user ? > >> > > Returning a non null value is the think to do, see : > > http://tapestry.apache.org/tapestry5/tapestry-core/guide/event.html > > > > If you want to return the same page, just return the page object > > (available thanks to ComponentResources#getPage() ). > > Perhaps if you return this, T5 will do the job for you. > > > --- original Nachricht Ende ---- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
