Is there a way of knowing if Tapestry is page rendering or event handling (was: Page render event URLs with large optional context parameter)

2010-02-22 Thread Blower, Andy
? (pretty simply by setting a Boolean flag in setup render..) Thanks, Andy -Original Message- From: Kalle Korhonen [mailto:kalle.o.korho...@gmail.com] Sent: 16 February 2010 18:22 To: Tapestry users Subject: Re: Page render event URLs with large optional context parameter If you

Re: Is there a way of knowing if Tapestry is page rendering or event handling (was: Page render event URLs with large optional context parameter)

2010-02-22 Thread Thiago H. de Paula Figueiredo
On Mon, 22 Feb 2010 10:20:59 -0300, Blower, Andy andy.blo...@proquest.co.uk wrote: So, how can I detect if Tapestry is rendering (and which page) from within the pages' onPassivate method? Take a look at the decode* methods in ComponentEventLinkEncoder. -- Thiago H. de Paula Figueiredo

RE: Is there a way of knowing if Tapestry is page rendering or event handling (was: Page render event URLs with large optional context parameter)

2010-02-22 Thread Blower, Andy
(was: Page render event URLs with large optional context parameter) On Mon, 22 Feb 2010 10:20:59 -0300, Blower, Andy andy.blo...@proquest.co.uk wrote: So, how can I detect if Tapestry is rendering (and which page) from within the pages' onPassivate method? Take a look at the decode

Re: Is there a way of knowing if Tapestry is page rendering or event handling (was: Page render event URLs with large optional context parameter)

2010-02-22 Thread Thiago H. de Paula Figueiredo
On Mon, 22 Feb 2010 13:05:52 -0300, Blower, Andy andy.blo...@proquest.co.uk wrote: Thanks for the reply Thiago. I'm pretty familiar with the methods in CELE (as I call it) but I'm not seeing what you're getting at. Is there something that Tapestry puts in the environment? AFAIK, no. You

Page render event URLs with large optional context parameter

2010-02-16 Thread Blower, Andy
I may have enquired about this a while back, but I put it on the back burner and am only just returning to it now. Basically I have a page with an activation context which is not bookmarkable (relies on session info) without an extra parameter in the activation context which contains all the

Re: Page render event URLs with large optional context parameter

2010-02-16 Thread Kalle Korhonen
If you have a limited number of pagelinks referring to the same page, maybe you could just contruct them by hand and just return null in onPassivate. I.e. store the initial context to @Property initialContext and then render the page links with t:pagelink page=mypage context=initialContext/ -