It seems that you could override the session persistence strategy and replace the usage of http session with Shiro's session -e.g. the implementation seems to be pretty straightforward e.g. inside of Tapestry , look at SessionApplicationStatePersistenceStrategy ( http://www.koders.com/java/fidD25B085EE97B4962767F605CD9762E1E9A50DFA6.aspx?s=base64 ).
Cheers, Alex K On Wed, Aug 8, 2012 at 10:51 AM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > So you are using native Shiro session management. Tapestry / Servlet API > don't support that. > If you use a 'real' JEE server like Glassfish, web sessions are clustered > / cached properly for you, > without Shiro native sessions or customDAO etc. > > You cannot use Shiro native session management and expect it to propagate > to Servlet sessions. This just doesn't make sense. > > > On Aug 8, 2012, at 10:48 AM, kata wrote: > > > i > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
