Hi Les,
Thank your for your quick answer - I applied your suggested changes and
used the debugger. The CacheManager is correctly applied to the realm
and works fine.
However, the misconception was on my side. I thought that the caching is
used for authentication too (but it isn't in 1.1 according to your last
post).
My two remaining questions are
- Do you already know when Shiro 1.2 will be released?
- Will there be any breaking changes in Shiro 1.2 which would make the
integration in third party frameworks such as Wicket-Shiro difficult?
Philipp
In your current config, there is no need to set the session mode or
the ServletContainerSessionManager - those two are already Shiro's
default settings.
In the securityManager() method, after you've set the realm, then call
sm.setCacheManager(shiroCacheManager()) and that should work fine.
If you connect a debugger, can you see that the CacheManager has been
propagated to the realm?
Cheers,
Les
P.S. Authorization Caching is available in 1.1. Authentication
Caching is available in trunk now and will be generally available in
Shiro 1.2
