[jboss-jira] [JBoss JIRA] (WFLY-9966) local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
Paul Ferraro (JIRA)
issues at jboss.org
Tue Mar 6 14:27:00 EST 2018
[ https://issues.jboss.org/browse/WFLY-9966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro closed WFLY-9966.
------------------------------
Resolution: Rejected
jndi-name was intentionally removed from the subsystem schema.
By default, Infinispan caches are bound to JNDI using the name:
"java:jboss/infinispan/cache/_container-name_/_cache-name_"
You can use a resource-ref or resource-env-ref to link the global jndi name to an application specific namespace with any name that you like.
> local-cache doesn't allow jndi-name attribute any more in wildfly 12, but it still supports in wildfly 11
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9966
> URL: https://issues.jboss.org/browse/WFLY-9966
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: dungtri pham
> Assignee: Paul Ferraro
>
> I use to have my local cache defined in wildfly 10, 11 like below:
> <cache-container name="mycache" default-cache="my_device_cache">
> <local-cache name="my_device_cache" jndi-name="java:/cache/device/status">
> <file-store passivation="false" preload="true" purge="false" shared="true"/>
> </local-cache>
> </cache-container>
> Now, it blows up in wildfly 12 and complains about jndi-name isnt allowed attribute for the local-cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list