[
https://issues.apache.org/jira/browse/SHIRO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860568#action_12860568
]
Nariman commented on SHIRO-95:
------------------------------
my solution to set cache name for securityManager is
/**
*
* @author Nariman
*/
public class SecurityManager extends
org.apache.shiro.web.DefaultWebSecurityManager{
public SecurityManager(){
super();
}
public void setActiveSessionsCacheName(String activeSessionsCacheName) {
SessionManager sessionManager = this.getSessionManager();
((CachingSessionDAO)((DefaultSessionManager)sessionManager).getSessionDAO()).setActiveSessionsCacheName(activeSessionsCacheName);
}
}
> Specifying my own Cache in ShiroFilter not working
> --------------------------------------------------
>
> Key: SHIRO-95
> URL: https://issues.apache.org/jira/browse/SHIRO-95
> Project: Shiro
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.0.0
> Reporter: Andy Tripp
> Priority: Minor
> Fix For: 1.0.0
>
>
> When I specify my own CacheManager and Cache object in my ShiroFilter, the
> default Cache manager is being used anyway. See thread "need help pluggin in
> my own session cache" in August and September 2009 archives of the Shiro
> mailing list for details.
> This is another order-of-operations issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
