[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-2048) Determine how to specify an Infinispan CacheManager in an SFSB configuration

[Paul Ferraro (JIRA)]

    [ https://jira.jboss.org/browse/EJBTHREE-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535025#action_12535025 ] 

Paul Ferraro commented on EJBTHREE-2048:
----------------------------------------

Another option
C) Embed the cache manager name within the name attribute, using some delimiter (e.g. ":")
e.g.
@CacheConfig(name = "sfsb")
@CacheConfig(name = "foo:sfsb")

The 1st example would use the sfsb cache from the default cache manager.
The 2nd example would use the sfsb cache from the "foo" cache manager.
The logic to parse the cache manager name from the cache name would reside in the Infinispan CacheManagerLocator.                

> Determine how to specify an Infinispan CacheManager in an SFSB configuration
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2048
>                 URL: https://jira.jboss.org/browse/EJBTHREE-2048
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: cache, Clustering
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>
> See JBAS-7838.
> The AS's integration with JBC supports a single CacheManager with multiple name cache configurations. The EJB3 @CacheConfig annotation's "name" attribute is used to specify which cache configuration to use for caching.
> Because of JBAS-7838, with Infinispan it's possible there will be multiple CacheManagers. That means
> 1) there needs to be a mechanism to find the correct one
> 2) it's theoretically possible the same cache configuration name will appear in two different CacheManager instances.
> Using a single attribute on an annotation to express this doesn't map cleanly. We need to sort this so we can design how the AS will expose multiple cache managers.
> Options:
> A) Add another attribute to @CacheConfig. Not really clean, as this is a general purpose annotation, and this attribute would be "Infinispan-centric".
> B) Just leave @CacheConfig as is, have the AS's Infinispan integration reject configurations that use the same cache configuration name in two different CacheManager instances, and have the CacheManagerLocator class in ha-server-api expose a method to find the CacheManager that exposes the config named in @CacheConfig.name.
> C) ???

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira