[
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.
