[jboss-jira] [JBoss JIRA] (WFLY-11486) Split cache-container resource into local vs clustered resources

Paul Ferraro created WFLY-11486: ----------------------------------- Summary: Split cache-container resource into local vs clustered resources Key: WFLY-11486 URL: https://issues.jboss.org/browse/WFLY-11486 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 15.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro At the last clustering F2F, we discussed splitting Infinispan's DefaultCacheManager into separate local vs clustered variants. A local cache manager would no longer be able to contain clustered caches; and a clustered cache manager will no longer be able to contain local caches. Supporting this will require a change to the Infinispan subsystem management model. Currently, there is a singleton /cache-container=* resource, with the following children: /cache-container=*/local-cache=* /cache-container=*/invalidation-cache=* /cache-container=*/replicated-cache=* /cache-container=*/distributed-cache=* /cache-container=*/scattered-cache=* This jira would change these resource to the following: /local-cache-container=*/local-cache=* /clustered-cache-container=*/invalidation-cache=* /clustered-cache-container=*/replicated-cache=* /clustered-cache-container=*/distributed-cache=* /clustered-cache-container=*/scattered-cache=* Only the clustered-cache-container variant would support a transport=jgroups child resource. The existing transport=none would become obsolete, and no longer a source of confusion. N.B. This is not a feature, but a requirement to support a future release of Infinispan -- This message was sent by Atlassian Jira (v7.12.1#712002)