On Thu, May 21, 2009 at 6:01 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote:
>> I am creating a web application using Tapestry for the GSoC. >> I was wondering what is best way to fit security requirements of a mere >> application (login/password/roles). > > This has been discussed in this list before. Check the archives > (http://www.nabble.com/Tapestry---User-f340.html) for some ideas. > Usually they are centered around a RequestFilter or a > ComponentClassTransformer. > >> How to keep and pass the user data from page to page ? I think chenillekit-access could help here, we have had issues with the new host at formos, mainly due to regular jobs constraints which caused a lot of delay in handling them. A 1.1.x release is due in some time, hopefully soon. I'm very interested in feedback from you about the module. Regards -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
