[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-316) Add aliasing capability to DefaultCacheManager

[Paul Ferraro (JIRA)]

     [ https://jira.jboss.org/browse/ISPN-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro resolved ISPN-316.
-------------------------------

      Assignee: Paul Ferraro  (was: Brian Stansberry)
    Resolution: Rejected


This feature is no longer needed.  The aliasing requirements of the AS are actually at the cache *manager* level, not at the cache level.  This is implemented in DefaultCacheContainerRegistry in the ha-server-ispn JBCLUSTER project.

> Add aliasing capability to DefaultCacheManager
> ----------------------------------------------
>
>                 Key: ISPN-316
>                 URL: https://jira.jboss.org/browse/ISPN-316
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>            Priority: Minor
>             Fix For: 5.0.0.BETA1
>
>
> The JBoss AS impl of the JBC CacheManager supports aliasing of cache configuration names. DefaultCacheManager can do the same. Helpful for preserving configuration compatibility across releases, e.g. an EJB3 bean class annotated with @CacheConfig(name="jboss.cache:service=EJB3SFSBClusteredCache") to work in AS 4.2 still works in AS 5 because I made "jboss.cache:service=EJB3SFSBClusteredCache" an alias for "sfsb-cache".
> This doesn't affect the CacheManager API; it's an implementation detail; just inject a map of aliases and then resolve any unknown configuration names against it.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira