[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=13107666#comment-13107666 ] 

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

Is there any documentation that explains how the infinispan-query modules would be re-added? I can't find any.

I wanted to add the necessary modules to WildFly 10.0.0.Beta2 and play with the new continuous query feature that was added in Infinispan 8. But the way the Infinispan project packages the modules seemingly makes it impossible for them to actually work. I used the infinispan-as-embedded-modules zip file, since that's what the Infinispan download page links to. I've tried putting the modules in $WFLY/modules and in $WFLY/modules/system/layers/base, but the result is the same both ways. In order to make the Infinispan classes visible to the deployment, I have to add the necessary modules (org.infinispan, org.infinispan.commons, and org.infinispan.query) as dependencies in jboss-deployment-structure.xml. The problem is that the zip contains modules with the "ispn-8.0" slot instead of the "main" slot. So,
* if I don't specify a slot for any of the modules, deployment fails with "Caused by: org.jboss.modules.ModuleNotFoundException: org.infinispan.query:main" as one would expect.
* if I specify ispn-8.0 for all of the modules, deployment fails with "Caused by: java.lang.IllegalArgumentException: Can not set org.infinispan.AdvancedCache field xxx to org.jboss.as.clustering.infinispan.DefaultCache", which makes sense because WildFly uses the main slot when it starts Infinispan (and there is no way to make it use a different slot, as far as I can tell).
* if I specify ispn-8.0 for just the query module and leave the others on the main slot, deployment fails with "Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "org/infinispan/Cache""

Am I missing something here? Or is the Infinispan project just not packaging these modules correctly? If it's an Infinispan problem, I'll go raise an issue in their tracker.

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