Yeah, because of INI's simplicity, config lines are executed immediately in the order they are defined; there is no 'definition' concept where all this stuff is executed in a second pass due to the complexity that would introduce, especially since Spring/Guice/JBossXML/etc can do that more effectively than we could. This is why order matters so much for INI config.
Your comments though aren't the first related to configuring native sessions and the effects ordering has. Perhaps it'd be better to get rid of the 'sessionMode' convenience property entirely to ensure things are more explicit/known. Anyway, I'm glad that worked! Cheers, Les On Mon, Jun 13, 2011 at 4:19 PM, juminoz <[email protected]> wrote: > Thanks Les. That solved the problem. I think my problem was with the order of > initialization when using "native" mode. > > Jack > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Problem-with-sessionDAO-and-WebFilter-tp6464439p6472174.html > Sent from the Shiro User mailing list archive at Nabble.com.
