shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalle Korhonen (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (SHIRO-201) SessionsSecurityManager destroy() doesn't call super.destroy()
Date Fri, 15 Oct 2010 16:52:32 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kalle Korhonen reassigned SHIRO-201:
------------------------------------

    Assignee: Kalle Korhonen

> SessionsSecurityManager destroy() doesn't call super.destroy()
> --------------------------------------------------------------
>
>                 Key: SHIRO-201
>                 URL: https://issues.apache.org/jira/browse/SHIRO-201
>             Project: Shiro
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Jared Stehler
>            Assignee: Kalle Korhonen
>
> The destroy method in org.apache.shiro.mgt.SessionsSecurityManager does not make a call
to super.destroy().  This is preventing the cache manager from being destroyed, as it lives
further up the inheritance chain.  All other *SecurityManager.destroy() methods properly invoke
super.destroy().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message