Re: Login Filter,

2009-12-11 Thread sandeepraj singh
...@tapestry.apache.org -- View this message in context: http://old.nabble.com/Login-Filter%2C-tp26525297p26742769.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users

Re: Login Filter,

2009-12-09 Thread sandeepraj singh
- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- View this message in context: http://old.nabble.com/Login-Filter%2C-tp26525297p26708778.html Sent from

Login Filter,

2009-11-26 Thread sandeepraj singh
be redirected to the login page. Could you suggest a good strategy. Can we make such checks in myFilter which extends Tapestry5 filter? Thanks sandeep -- View this message in context: http://old.nabble.com/Login-Filter%2C-tp26525297p26525297.html Sent from the Tapestry - User mailing list archive

Re: Login Filter,

2009-11-26 Thread Ulrich Stärk
Use a ComponentRequestFilter. That way you can handle component events and page render requests inside the same filter. HTH, Uli Am 26.11.2009 10:03 schrieb sandeepraj singh: Hi, I have the following requirement for my application Develop a Tapestry login check Filter which (a) Avoids

Re: Login Filter,

2009-11-26 Thread Juan E. Maya
to the login page. (b) After session expiry if we do any action, It should be redirected to the login page. Could you suggest a good strategy. Can we make such checks in myFilter which extends Tapestry5 filter? Thanks sandeep -- View this message in context: http://old.nabble.com/Login-Filter

Re: Login Filter,

2009-11-26 Thread Thiago H. de Paula Figueiredo
Em Thu, 26 Nov 2009 07:27:16 -0200, Juan E. Maya maya.j...@gmail.com escreveu: or Tapestry-Spring-Security Integration I don't recommend it because the checks are made in the setup render event, *after* the activate (onActivate()) one. It does not cover action requests, so I created my

Re: Login Filter,

2009-11-26 Thread Thiago H. de Paula Figueiredo
Em Thu, 26 Nov 2009 07:18:53 -0200, Ulrich Stärk u...@spielviel.de escreveu: Use a ComponentRequestFilter. That way you can handle component events and page render requests inside the same filter. It could be a Dispatcher too. The wiki has a nice explanation:

Re: Login Filter,

2009-11-26 Thread Alfonso Quiroga
Thiago: [...]your dispatcher must be added before the RootPath[...] Is that neccesary? RootPath I think is when you go to /, this is Index page, and we suppose Index doesn't need security. So I use my security dispatcher AFTER RootPath. Thanks On Thu, Nov 26, 2009 at 8:41 AM, Thiago H. de Paula

Re: Login Filter,

2009-11-26 Thread Thiago H. de Paula Figueiredo
Em Thu, 26 Nov 2009 15:15:13 -0200, Alfonso Quiroga alfonsose...@gmail.com escreveu: Thiago: [...]your dispatcher must be added before the RootPath[...] Is that neccesary? RootPath I think is when you go to /, this is Index page, and we suppose Index doesn't need security. So I use my