Ah - yes, that issue has been resolved in Shiro 1.2. If you configure a non-servlet-container-based SessionManager, the sessions are considered 'native' automatically.
As for 1.2, we haven't made the announcement yet because I'm still organizing the announcement + documentation, but the binaries have already propagated to Maven central. You should be able to test with 1.2.0 right now. HTH, -- Les Hazlewood CTO, Katasoft | http://www.katasoft.com | 888.391.5282 twitter: @lhazlewood | http://twitter.com/lhazlewood katasoft blog: http://www.katasoft.com/blogs/lhazlewood personal blog: http://leshazlewood.com On Tue, Jan 24, 2012 at 10:19 AM, Mike K <[email protected]> wrote: > Thanks Les, > But that is not enough. If you do that the sessions don't get touched. You > have to setSessionMode("native") for sessions to be touched in the > org.apache.shiro.web.servlet.AbstractShiroFilter#updateSessionLastAccessTime. > I have a work around and will be waiting for 1.2 to release - when do you > think that would happen BTW? I have a crowd integration that I would like > to contribute, but its a little ugly within 1.1. > > Mike. > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/setSessionManager-and-setSessionMode-don-t-play-nice-in-DefaultWebSecurityManager-tp7218566p7221234.html > Sent from the Shiro User mailing list archive at Nabble.com.
