You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2008/11/05 19:51:44 UTC
[jira] Created: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Missing org.jsecurity.cache.ehcache.EhCacheManager
--------------------------------------------------
Key: JSEC-24
URL: https://issues.apache.org/jira/browse/JSEC-24
Project: JSecurity
Issue Type: Bug
Affects Versions: 0.9-RC1
Reporter: Alan Cabrera
Assignee: Les Hazlewood
Fix For: 0.9
We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645701#action_12645701 ]
Alan Cabrera commented on JSEC-24:
----------------------------------
If Ehcache is not in the classpath then there is no cache manager. This breaks SimpleAccountRealm and anything that inherits from it, i.e. PropertiesRealm, the default realm. So, if Ehcache is not in the classpath, the default behavior of JSecurity is broken.
IMO, we should either make a hard dependency on Ehcache or make HashtableCacheManager the default cache manager.
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646008#action_12646008 ]
Alan Cabrera commented on JSEC-24:
----------------------------------
Will move EHCache back to its original place for v0.9
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Cabrera reassigned JSEC-24:
--------------------------------
Assignee: Alan Cabrera (was: Les Hazlewood)
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Moved: (KI-3) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KI-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Cabrera moved JSEC-24 to KI-3:
-----------------------------------
Fix Version/s: (was: 0.9)
Affects Version/s: (was: 0.9-RC1)
Key: KI-3 (was: JSEC-24)
Project: Ki (was: JSecurity)
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: KI-3
> URL: https://issues.apache.org/jira/browse/KI-3
> Project: Ki
> Issue Type: Bug
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647082#action_12647082 ]
Les Hazlewood commented on JSEC-24:
-----------------------------------
I wholeheartedly agree with the sentiments on the mailing list about making EhCache an optional dependency.
My only recommendation is that because HashtableCacheManager is not suitable for production use because references are never relinquished or expired, thereby causing a memory leak, that we create a WeakReferenceCacheManager (or something more appropriately named) that will use Weak References to ensure a memory leak is much less likely to occur.
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood reassigned JSEC-24:
---------------------------------
Assignee: Les Hazlewood (was: Alan Cabrera)
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647314#action_12647314 ]
Les Hazlewood commented on JSEC-24:
-----------------------------------
What is left to be done on this before it can be closed out?
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Grzegorz Borkowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646113#action_12646113 ]
Grzegorz Borkowski commented on JSEC-24:
----------------------------------------
About one month ago I wanted to put similar issue here, but not had much time then to proceed.
I've got NPE all the time, and finally I found out that it was because of missing Cache, because EHCache was not on a classpath - see the description of my problem posted on JSecurity mailing list:
http://n2.nabble.com/Problematic-first-steps-with-JSecurity-td1316205.html#a1348621
Using EHCache as default cache provider additionally introduces dependency on the library, which should be really optional. I thing that for many cases (prototypes, tests etc) the simple HashMap-based cache should be sufficient. So I vote for making the HashtableCacheManager the default implementation - this will be much more clear situation.
BTW: Why "HashtableCacheManager", not "HashmapCacheManager"? Does it use internally Hashtable? Or it is just a name?
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Cabrera reopened JSEC-24:
------------------------------
Maven build is still broken. Also, when you check in code, please make sure that the issue numbers are in the checkin comment.
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647318#action_12647318 ]
Les Hazlewood commented on JSEC-24:
-----------------------------------
I'm not sure why it is considered missing?
It is located in <jsecurity root>/import/trunk/support/ehcache/src/org/jsecurity/cache/ehcache/EhCacheManager.java
It is not in the main trunk/src directory because it contains a 3rd party library. The ant build was altered to handle this special case, and it will be modified again when it is removed as a forced dependency after 0.9 final.
Is there anything left to be done still?
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647107#action_12647107 ]
Alan Cabrera commented on JSEC-24:
----------------------------------
The current thinking is to make EhCache the default cache, we it was for the previous candidates. Then for 1.0 we can discuss an alternative.
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood closed JSEC-24.
-----------------------------
Resolution: Fixed
Closing per mailing list discussion. Can create a new issue later if we want to address using Maven to build (beyond providing a pom for end users for bundling purposes).
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JSEC-24) Missing
org.jsecurity.cache.ehcache.EhCacheManager
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood resolved JSEC-24.
-------------------------------
Resolution: Fixed
I re-enabled the previously-commented code.
cd'ing into the <root>/import/trunk directory and running 'ant clean && ant' will enable the full build successfully.
> Missing org.jsecurity.cache.ehcache.EhCacheManager
> --------------------------------------------------
>
> Key: JSEC-24
> URL: https://issues.apache.org/jira/browse/JSEC-24
> Project: JSecurity
> Issue Type: Bug
> Affects Versions: 0.9-RC1
> Reporter: Alan Cabrera
> Assignee: Les Hazlewood
> Fix For: 0.9
>
>
> We seem to be missing org.jsecurity.cache.ehcache.EhCacheManager. The CachingSecurityManager seems to need it. For time time being I have commented out the code in anticipation to you fixing the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.