(Thanks Alexandr) Indeed, that's what I thought. I've already done as you outline, and it looks like it might be a bug as the subsequent calls to ThreadLocal.get() are getting a different instance and hence throwing the exception above. That said, it seems that there are loads of instances of people using Shiro in a similar configuration to mine, so I figure it should be a well-trodden path (so it follows the likelihood of it being a bug is slim), so I was hoping to bump this thread to see if someone with more experience of this area of the codebase could make sense of what I was seeing in my debugger?
-- View this message in context: http://shiro-user.582556.n2.nabble.com/Do-you-have-to-SecurityUtils-setSecurityManager-in-a-web-app-to-use-shiro-tag-library-tp7114798p7171946.html Sent from the Shiro User mailing list archive at Nabble.com.
