[infinispan-issues] [JBoss JIRA] (ISPN-7343) Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
Sanne Grinovero (JIRA)
issues at jboss.org
Mon Jan 9 06:18:00 EST 2017
[ https://issues.jboss.org/browse/ISPN-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero updated ISPN-7343:
----------------------------------
Reporter: Sanne Grinovero (was: Sebastian Łaskawiec)
> Allow using Hibernate Search, Hibernate ORM, Hibernate OGM and Infinispan + Infinispan Query in the same app in Wildfly
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-7343
> URL: https://issues.jboss.org/browse/ISPN-7343
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying, WildFly modules
> Reporter: Sanne Grinovero
> Priority: Minor
>
> We should make it easier to use all those libraries in a single app on WildFly.
> This is a tricky request, as Infinispan Query exposes its own version of Hibernate Search as public API: people need to use it directly to use embedded query.
> Not least it requires exposing:
> * index mapping annotations from Hibernate Search
> * Usage of the Hibernate Search querybuilder helpers (optional)
> * Direct usage of the Apache Lucene classes, in turn exposed as well as public API by Hibernate Search
> When wanting to use Hibernate Search directly as well (with Hibernate ORM), one needs not only to choose a version which is compatible with both, but one also needs to make sure that the WildFly modules are all using the same module id; the problem being one should not use multiple copies of the module, as the Infinispan project re-distributes its own copy of such modules.
> Picking a compatible version is limiting but not hard; editing all module XML definitions is not very nice though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the infinispan-issues
mailing list