Thiago, in my app, the session can exist but not be valid, so I have a custom annotation that has a parameter that I want to trigger this check. I also do not have ComponentRequestFilter of my own defined, isn't method advisor and a custom annotation enough?
On Sep 19, 2011, at 1:03 PM, Thiago H. de Paula Figueiredo wrote: > Wouldn't it be easier for you to use a session state object to check this > (set in a ComponentRequestFilter)? I don't feel checking for all @Persist'ed > fields for null is correct, as I guess there are situations in which having > all them null is valid. > > -- > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
