[jboss-jira] [JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

[Rich DiCroce (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107961#comment-13107961 ] 

Rich DiCroce commented on WFLY-4695:
------------------------------------

Thanks for the replies. Tristan, how concrete are the plans for that side-along subsystem? Is there an open issue for it? What does the timeline look like?

The lack of that subsystem is a huge problem for my application. I don't really care about being able to use a different Infinispan version than what WildFly is using, but I very much care about integration with the application server. And the modules currently provided by the Infinispan project effectively make that impossible. Sure, I can run all of Infinispan inside my application. I can define the necessary thread pools through the EE subsystem and I can probably get hold of the appropriate TransactionManagerLookup implementation somehow. But I can't see any way around having a completely separate JGroups channel, because the Infinispan modules bundle their own version in a separate slot, which means I can't piggyback on the channel that WildFly is using for everything else. That in turn means that different components would have different opinions about the topology of the cluster, and that feels like a disaster waiting to happen.

Besides, if I have to do all of the integration myself, that kinda defeats the purpose of having an application server, don't you think? :)

> 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)