You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Jeremy Haile (JIRA)" <ji...@apache.org> on 2009/03/02 06:35:15 UTC

[jira] Created: (JSEC-65) Allow EhCacheManager to use singleton CacheManager instance

Allow EhCacheManager to use singleton CacheManager instance
-----------------------------------------------------------

                 Key: JSEC-65
                 URL: https://issues.apache.org/jira/browse/JSEC-65
             Project: JSecurity
          Issue Type: Improvement
          Components: Caching
            Reporter: Jeremy Haile
             Fix For: 1.0


Currently we create a new CacheManager if one is not injected for reasons described in code comments in EhCacheManager.init().  However, in some cases it is useful to simply use the EhCache CacheManager singleton.  A couple of examples: 1) When clustering with Terracotta, if you use the singleton instance it is automatically clustered  2) It is convenient to configure all of your caches in a single ehcache.xml file, rather than needing multiple ehcache files for each CacheManager instance.

We should add a property that determines whether or not the EhCacheManager uses the singleton CacheManager or instantiates a new one. 

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


[jira] Assigned: (JSEC-65) Allow EhCacheManager to use singleton CacheManager instance

Posted by "Jeremy Haile (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSEC-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Haile reassigned JSEC-65:
--------------------------------

    Assignee: Jeremy Haile

> Allow EhCacheManager to use singleton CacheManager instance
> -----------------------------------------------------------
>
>                 Key: JSEC-65
>                 URL: https://issues.apache.org/jira/browse/JSEC-65
>             Project: JSecurity
>          Issue Type: Improvement
>          Components: Caching
>            Reporter: Jeremy Haile
>            Assignee: Jeremy Haile
>             Fix For: 1.0
>
>
> Currently we create a new CacheManager if one is not injected for reasons described in code comments in EhCacheManager.init().  However, in some cases it is useful to simply use the EhCache CacheManager singleton.  A couple of examples: 1) When clustering with Terracotta, if you use the singleton instance it is automatically clustered  2) It is convenient to configure all of your caches in a single ehcache.xml file, rather than needing multiple ehcache files for each CacheManager instance.
> We should add a property that determines whether or not the EhCacheManager uses the singleton CacheManager or instantiates a new one. 

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


[jira] Moved: (KI-54) Allow EhCacheManager to use singleton CacheManager instance

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera moved JSEC-65 to KI-54:
------------------------------------

    Fix Version/s:     (was: 1.0)
      Component/s:     (was: Caching)
              Key: KI-54  (was: JSEC-65)
          Project: Ki  (was: JSecurity)

> Allow EhCacheManager to use singleton CacheManager instance
> -----------------------------------------------------------
>
>                 Key: KI-54
>                 URL: https://issues.apache.org/jira/browse/KI-54
>             Project: Ki
>          Issue Type: Improvement
>            Reporter: Jeremy Haile
>            Assignee: Jeremy Haile
>
> Currently we create a new CacheManager if one is not injected for reasons described in code comments in EhCacheManager.init().  However, in some cases it is useful to simply use the EhCache CacheManager singleton.  A couple of examples: 1) When clustering with Terracotta, if you use the singleton instance it is automatically clustered  2) It is convenient to configure all of your caches in a single ehcache.xml file, rather than needing multiple ehcache files for each CacheManager instance.
> We should add a property that determines whether or not the EhCacheManager uses the singleton CacheManager or instantiates a new one. 

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