Nice! Works perfectly! I got it all with one single line(i.e. way better than my last solution...)
Thanks! 2008/6/16 Howard Lewis Ship <[EMAIL PROTECTED]>: > You can cheat by taking a page instance, casting it to Component (or > to ComponentResourcesAware) and getting it's ComponentResources that > way. You can then invoke the discardPersistentFieldChanges() method > directly. > > If you know the name of a page, the ComponentSource service has a > method, getPage(), that returns Component. > > On Mon, Jun 16, 2008 at 1:06 PM, Marcelo Lotif <[EMAIL PROTECTED]> wrote: >> Hi guys, >> I was getting around some issues in my application regarding to the >> size of the session, and i found on the tapestry site that you can >> clean the persistent data of a page by injecting ComponentResources >> and running discardPersistentFieldChanges(), but i also noted that >> this can only be done by a page to clean itself, not to clean other >> pages (like a menu bar that calls a page and wants to clean the last >> one). I was wondering how useful would be if the method was overloaded >> by discardPersistentFieldChanges(Component page) or >> discardPersistentFieldChanges(String pageName) in the >> ComponentResources. What do you tapestry committers think about it? >> >> -- >> Atenciosamente, >> Marcelo Lotif >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Atenciosamente, Marcelo Lotif --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
