On Thu, 19 Aug 2010 17:53:56 -0300, Rich M <rich...@moremagic.com> wrote:
Actually I spoke a little too soon about the persistent fields. I'm not
really clear on how that is solved by a ComponentRequestFilter, other
than it's a good place to do it. ComponentSource doesn't provide any
means with which to clear persistent fields.
From ComponentSource you get the page instance (a Component). It has a
getComponentResources() method. From there, you can invoke
discardPersistentFieldChanges().
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
