Hi Aj,
Since you are using tapestry in a portlet, please read this to
understand your problem:
http://jakarta.apache.org/tapestry/tapestry-portlet/coding-issues.html
Hope that makes everything clear
Richard.
Aj Gregory wrote:
You're right that would be nice (and expected), but if I call
setObject(...) on the current page in the listener it won't be set
when the page is rendered again. From what I can tell by logging
messages in PageAttachListener and PageDetachListener the page is
re-acquired from the pool before rendering the result, which wipes out
any non-persistent values.
I don't want to persist the result value since I just want it for
rendering the next time and then I want it to go away.
Again, I'm using this in a portlet so I'm not sure if this is an issue
with tapestry in portlets or in general...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
