You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2009/01/11 08:49:59 UTC
[jira] Resolved: (JSEC-40) Remove hard-dedepency of EhCache on core
API
[ https://issues.apache.org/jira/browse/JSEC-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood resolved JSEC-40.
-------------------------------
Resolution: Fixed
Assignee: Les Hazlewood
Fixed. The core API now relies on a DefaultCacheManager instance at startup, which provides production-safe (memory-leak-free) SoftMapCache instances. Ehcache is still an option, but it now must be explicitly configured if an end-user wants to use it.
> Remove hard-dedepency of EhCache on core API
> --------------------------------------------
>
> Key: JSEC-40
> URL: https://issues.apache.org/jira/browse/JSEC-40
> Project: JSecurity
> Issue Type: Improvement
> Components: Caching
> Affects Versions: 1.0
> Reporter: Les Hazlewood
> Assignee: Les Hazlewood
> Fix For: 1.0
>
>
> Per this thread: http://markmail.org/message/szkvpl2vxlj6zwno
> We'd like to ensure hard dependencies on Ehcache are removed from the Core API, perhaps defaulting to a standalone memory-based CacheManager that is suitable for production environments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.