[
https://jira.jboss.org/browse/EJBTHREE-2048?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on EJBTHREE-2048:
--------------------------------------------
C) sounds ok.
The way we do it already to an extent imposes a requirement on the user to understand how
the CacheManager and EJB3 integrate, if they want to move beyond the default
"sfsb-cache". So now they *may* need to know a bit more, but the documentation
on how to do it would come from the same place.
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