Re: DiscardAfter on component level
On Wed, 28 Sep 2011 02:53:17 -0300, mem wrote: Hello, Hi! Maybe something like this would be helpful for other applications as well and be added to Tapestry, where to request such a "feature". Sounds interesting to me. :) Tapestry 5's JIRA is the place for filing suggestions and patches: https://issues.apache.org/jira/browse/TAP5. -- 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
DiscardAfter on component level
Hello, is there the possibility to put the DiscardAfter on a method on component level and only discard the persistent fields of this component and its subcomponents, but *NOT* from the page? I couldn't find any so i wrote a worker for my own annotation @DiscardComponentAfter which can be placed on either the page level or on component level. It's basically doing the same thing as the DiscardAfterWorker except that it's using completeId from the InternalComponentResourcesImpl class and directly injects the Request to be able to remove the session attributes as the method AbstractSessionPersistentFieldStrategy#discardChanges adds a colon at the end of the page name. Maybe something like this would be helpful for other applications as well and be added to Tapestry, where to request such a "feature". best regards Matt -- View this message in context: http://tapestry.1045711.n5.nabble.com/DiscardAfter-on-component-level-tp4847998p4847998.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
