[
https://issues.jboss.org/browse/WFLY-9463?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-9463:
------------------------------------
[~jwgmeligmeyling] Once started, the following Infinispan artifacts are available at the
following JNDI contexts:
* Cache Manager: java:jboss/infinispan/container/_container-name_/
* Cache configuration: java:jboss/infinispan/configuration/_container-name_/_cache-name_
* Cache: java:jboss/infinispan/cache/_container-name_/_cache-name_
If you'd rather not reference a global JNDI namespace in your application, you can use
a resource-ref or resource-env-ref to use an application-specific JNDI namespace.
Deprecate jndi-name attributes of Infinispan cache-container and
cache.
-----------------------------------------------------------------------
Key: WFLY-9463
URL:
https://issues.jboss.org/browse/WFLY-9463
Project: WildFly
Issue Type: Task
Components: Clustering
Affects Versions: 11.0.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 12.0.0.Beta1, 12.0.0.Final
There's no reason to expose these. These attributes add little value and are only a
source of confusion. Applications can always leverage a resource-ref or resource-env-ref
to customize the JNDI name.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)