Before I file a bug, I wanted to see if perhaps there is something wrong with
my understanding.
I configure and use an instance of DefaultWebSessionManager. I do this
because I need to configure my own DAO and I also want to control the path
and name of the cookie.
However, I noticed that for this configuration, the sessions were not
getting touched.
Setting the sessionMode to "native" actually caused all my SessionManager
changes to be unloaded. Maybe I can enforce the order in which setters are
applied in Spring, but it should not matter. Currently, though, it seems
that for DefaultWebSecurityManager setSessionMode("native") must be called
before the setSessionManager is called.
Mike.
--
View this message in context:
http://shiro-user.582556.n2.nabble.com/setSessionManager-and-setSessionMode-don-t-play-nice-in-DefaultWebSecurityManager-tp7218566p7218566.html
Sent from the Shiro User mailing list archive at Nabble.com.
