[
https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on WFLY-4695:
---------------------------------------
This is neither an Infinispan issue or a WildFly issue. Since Infinispan is also used
internally by WildFly for its clustering, replacing/changing it is dangerous. The
integration modules provided by Infinispan are for "side-along" installation,
and that is the reason for the dedicated slot. You cannot mix these modules with the ones
in the WildFly's 'main' slot. The downside of this is that applications need
to handle clustering/configuration/lifecycle on their own, instead of relying on the
container subsystem. It is our intention to also provide a side-along subsystem to
overcome this issue too.
Remove infinispan-query module and its dependencies
---------------------------------------------------
Key: WFLY-4695
URL:
https://issues.jboss.org/browse/WFLY-4695
Project: WildFly
Issue Type: Task
Components: Clustering
Reporter: Sanne Grinovero
Assignee: Paul Ferraro
Fix For: 10.0.0.Beta1
We generally expect people to use the version bundled by the Infinispan project, and
there are no strong reasons to include this in WildFly.
Also it makes it much harder to upgrade components such as Hibernate and Infinispan as
this components introduces strong coupling on several of these components, essentially
mandating that these are all upgraded in lock step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)