Ok, so this was caused by the module dependency
from org.hibernate.jipijapa-hibernate5 to org.hibernate. Seems I need to
create a 5.1-specific adapter module, too, and require that to be
configured by users via jboss.as.jpa.adapterModule.
2016-06-25 11:53 GMT+02:00 Gunnar Morling <gun...@hibernate.org>:
> Scott, all,
>
> As discussed I've started to work on a module ZIP which can be used to add
> Hibernate ORM 5.1 to an existing WildFly 10.0 instance (which comes with
> ORM 5.0). As module slot I'm using "5.1".
>
> Now I assumed that it'd be enough to set this property in persistence.xml:
>
> jboss.as.jpa.providerModule=org.hibernate:5.1
>
> Indeed I'm seeing that my new module is added as a dependency to the
> deployment, but the default ORM ("org.hibernate:main") is still being
> added, too. As a result I'm getting an exception due to incompatible
> Integrator classes (the 5.0 ORM tries to load the 5.1 integrator for Envers
> which is failing due to the incompatible class hierarchies).
>
> Do you have any idea why this is happening? I see that the module
> org.jboss.as.ejb3 has a dependency to module org.hibernate (no slot, i.e.
> "main"). May this be the cause? If so, what would I have to do to enable
> only my 5.1 module and not the default 5.0 one for a given deployment? Or
> any other idea?
>
> Thanks,
>
> --Gunnar
>
>
>
>
>
> 2016-06-08 17:16 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>
>> On 8 June 2016 at 16:08, Gunnar Morling <gun...@hibernate.org> wrote:
>> > It'd not only be a library, but an image containing WF with the latest
>> > Hibernate ORM. But as said, the module ZIP is more versatile and is
>> what I'd
>> > do.
>>
>> +1 for the priority on ZIP files.
>>
>> I had not understood that you meant to re-distribute a customized WF
>> image so I was quite confused :)
>>
>> >
>> > 2016-06-08 16:59 GMT+02:00 Sanne Grinovero <sa...@hibernate.org>:
>> >>
>> >> On 8 June 2016 at 08:11, Gunnar Morling <gun...@hibernate.org> wrote:
>> >> > 2016-06-07 15:51 GMT+02:00 Steve Ebersole <st...@hibernate.org>:
>> >> >
>> >> >> Too bad we can't just publish a Docker image.
>> >> >>
>> >> >
>> >> > We could do that, but I think we should have a solution for
>> non-Docker
>> >> > users, too.
>> >>
>> >> What's the point to package a library in a Docker image?
>> >>
>> >> >
>> >> >>
>> >> >> Is this something we'd publish somewhere (Nexus/Artifactory)?
>> >> >>
>> >> >
>> >> > Yes, we'd publish it in Nexus and also BinTray/SourceForge.
>> >> >
>> >> > People would download it, unzip it into the "modules" directory of
>> their
>> >> > WF
>> >> > instance and could start using the new ORM version (provided the
>> larger
>> >> > scheme of integration hasn't changed, so the JipiJapa bits in WF
>> >> > continue
>> >> > to work as is).
>> >> >
>> >> >
>> >> >> I know nothing about building a WF module ZIP. But if you are
>> >> >> willing
>> >> >> to do the work and it helps OGM etc, of course we would incorporate
>> it.
>> >> >>
>> >> >
>> >> > Ok, cool. I'll take a look then.
>> >> >
>> >> > On Tue, Jun 7, 2016 at 8:19 AM Gunnar Morling <gun...@hibernate.org>
>> >> > wrote:
>> >> >>
>> >> >>> Hi,
>> >> >>>
>> >> >>> As discussed by some of us during the No ORM meeting in May, it'd
>> be
>> >> >>> great
>> >> >>> if there was a module ZIP allowing people to easily upgrade
>> Hibernate
>> >> >>> ORM
>> >> >>> in the WildFly version they are using.
>> >> >>>
>> >> >>> Just the other day there was a blog post published [1] describing
>> how
>> >> >>> to
>> >> >>> use Hibernate ORM 5.2 in WF 10, essentially via Search & Replace on
>> >> >>> the
>> >> >>> existing module.xml files. We could do better than that, leaving
>> the
>> >> >>> original version intact and providing a new one with a specific
>> slot
>> >> >>> ("5.2") in the ZIP.
>> >> >>>
>> >> >>> That'd also be helpful for other projects such as Hibernate OGM
>> which
>> >> >>> already provide a module ZIP for WF but currently need to package
>> ORM,
>> >> >>> too,
>> >> >>> in case they need features from a later ORM version.
>> >> >>>
>> >> >>> If we all agree that's a good thing to have, I can help with
>> making it
>> >> >>> happen.
>> >> >>>
>> >> >>> Thanks,
>> >> >>>
>> >> >>> --Gunnar
>> >> >>>
>> >> >>> [1]
>> >> >>>
>> >> >>>
>> >> >>>
>> http://avolpe.github.io/docker/2016/06/05/docker-wildfly-hibernate-5.2.html
>> >> >>> _______________________________________________
>> >> >>> hibernate-dev mailing list
>> >> >>> hibernate-dev@lists.jboss.org
>> >> >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >> >>>
>> >> >>
>> >> > _______________________________________________
>> >> > hibernate-dev mailing list
>> >> > hibernate-dev@lists.jboss.org
>> >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> >
>> >
>>
>
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
