On Thu, May 21, 2009 at 12:50 PM, Thibaut Gadiolet <thibaut.gadio...@gmail.com> wrote: > Hi,
Hi! > 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 ? Usually, using @SessionState. > Should I use Tapestry mechanism to check access rights ? Like OnActivate for > each page ? use @SessionState ? You can use onActivate(), but then you would need to use it on every single page that needs a logged in user. > Or should I use Javascript and cookies ? You can't rely on them. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
