[ https://issues.redhat.com/browse/WFLY-13520?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13520: -------------------------------- Description: WildFly currently ships with the following modules: org.infinispan.client.hotrod: Hot Rod client org.infinispan.commons: Common API between the embedded and client modules org.infinispan: Embedded library org.infinispan.persistence.jdbc: JDBC Cache Store org.infinispan.persistence.remote: Hot Rod Cache Store To achieve feature parity with infinispan-server we would need to add the following modules: org.infinispan.cdi: CDI bindings org.infinispan.query: Query support org.infinispan.counter: Clustered counter support org.infinispan.lock: Clustered lock support org.infinispan.jcache: JCache API support was: EAP currently ships with the following modules: org.infinispan.client.hotrod: Hot Rod client org.infinispan.commons: Common API between the embedded and client modules org.infinispan: Embedded library org.infinispan.persistence.jdbc: JDBC Cache Store org.infinispan.persistence.remote: Hot Rod Cache Store To achieve feature parity with RHDG we would need to add the following modules: org.infinispan.cdi: CDI bindings org.infinispan.query: Query support org.infinispan.counter: Clustered counter support org.infinispan.lock: Clustered lock support org.infinispan.jcache: JCache API support (see EAP7-1197) For all of the above modules, RHDG engineering will donate the existing modules, including tests, to EAP. RHDG support and engineering will provide support for all use-cases relating to the components mentioned above, excluding the subsystems which would continue to be handled by EAP clustering. RHDG will provide documentation for the Infinispan API which can either be included in its modularized form or linked from the EAP documentation. It is understood that EAP will only use productized builds of the Infinispan/JGroups components that have already received RHDG QE sign-off. -- This message was sent by Atlassian Jira (v7.13.8#713008)