Martin, you really should be able to continue using @Persist and @SessionState. Both Shiro's subject.getSession() and the @Persist annotation store their values in the same http session. Is that not working for you ?
Cheers, Alex K On Wed, Aug 8, 2012 at 7:20 AM, kata <januszkiewicz.mar...@gmail.com> wrote: > Hi all, > > I am currently using shiro and the tapestry-security plugin to manage > sessions and persist data. Everything works fine when getting the session > by > SecurityUtils.getSubject().getSession(). However, this means that the > application is peppered with fragments of shiro-specific code. Since shiro > uses the servlet session API, is there a way to do this in a way that is > transparent to the application, and hopefully still allow me to use > annotations like @Persist and @SessionState? > > Thanks, > Martin > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Changing-default-session-behavior-tp5715141.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 > >
