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
