Then I must not be understanding. Why would you introduce a home-grown filter when tapestry-security would do the job for you?
On Feb 7, 2013, at 2:45 AM, Lance Java <lance.j...@googlemail.com> wrote: > I wasn't suggesting to include spring security in his project. I was > suggesting that an example of the filter I had suggested earlier could be in > most, if not all, tapestry security frameworks. For example, if you download > the tapestry-spring-security and search for "spring-security.loginform.url" > it should lead you to such a filter. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Keeping-the-session-alive-pattern-tp5719771p5719836.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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
