<div dir="ltr"><div><div><div>Scott,<br><br></div>if you do one last jipijapa release that adds "support" for hibernate5<br></div>hibernate guys could take that version and override it in wildfly 9 same way as they add new h5 modules.<br><br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 9:01 PM, Scott Marlow <span dir="ltr"><<a href="mailto:smarlow@redhat.com" target="_blank">smarlow@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/21/2015 02:11 PM, Emmanuel Bernard wrote:<br>
> Scott, No way to make ORM 5 work in 9 at all? With the user setting the additional slotted modules of course.<br>
<br>
</span><a href="https://github.com/scottmarlow/jipijapa/tree/JIPI-31" target="_blank">https://github.com/scottmarlow/jipijapa/tree/JIPI-31</a> contains the<br>
integration code that we will look at merging into WildFly 10. Are you<br>
looking for a custom WildFly 9.x branch or actual changes in WildFly 9<br>
(doesn't seem as likely to me but I don't control the schedule)?<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> It would help speed up the Hibernate 5 stream adoption and avoid a lot of duplicated work for 6+ months.<br>
><br>
>> On 21 mai 2015, at 16:36, Scott Marlow <<a href="mailto:smarlow@redhat.com">smarlow@redhat.com</a>> wrote:<br>
>><br>
>> Hibernate ORM 5.0 doesn't work yet on WildFly. Will push on this soon<br>
>> for WildFly 10.<br>
>><br>
>>> On 05/21/2015 07:30 AM, Sanne Grinovero wrote:<br>
>>> Hi all,<br>
>>> I'm attempting to deploy some integration tests on WildFly 9.0.0.CR1<br>
>>> to use a preview of Hibernate ORM version 5.<br>
>>><br>
>>> It seems the JPA deployer isn't allowing me to run such experiments:<br>
>>><br>
>>> # First experiment - providerModule set to custom module<br>
>>><br>
>>> In my first attempt, I create a custom set of jboss modules which<br>
>>> include the snapshot builds of ORM 5, add them to my standalone WF9<br>
>>> instance and set the persistence.xml property:<br>
>>> jboss.as.jpa.providerModule = my-custom-module-name<br>
>>><br>
>>> and then get:<br>
>>><br>
>>> Caused by: java.util.ServiceConfigurationError:<br>
>>> org.hibernate.integrator.spi.Integrator: Provider<br>
>>> org.hibernate.envers.boot.internal.EnversIntegrator not a subtype<br>
>>> at java.util.ServiceLoader.fail(ServiceLoader.java:231) [rt.jar:1.7.0_51]<br>
>>> at java.util.ServiceLoader.access$300(ServiceLoader.java:181) [rt.jar:1.7.0_51]<br>
>>> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:369)<br>
>>> [rt.jar:1.7.0_51]<br>
>>> at java.util.ServiceLoader$1.next(ServiceLoader.java:445) [rt.jar:1.7.0_51]<br>
>>> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.loadJavaServices(ClassLoaderServiceImpl.java:341)<br>
>>> at org.hibernate.integrator.internal.IntegratorServiceImpl.<init>(IntegratorServiceImpl.java:57)<br>
>>> at org.hibernate.boot.registry.BootstrapServiceRegistryBuilder.build(BootstrapServiceRegistryBuilder.java:247)<br>
>>> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildBootstrapServiceRegistry(EntityManagerFactoryBuilderImpl.java:520)<br>
>>> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:208)<br>
>>> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:188)<br>
>>> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:45)<br>
>>> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:57)<br>
>>> at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.<init>(TwoPhaseBootstrapImpl.java:38)<br>
>>> at org.jboss.as.jpa.hibernate4.HibernatePersistenceProviderAdaptor.getBootstrap(HibernatePersistenceProviderAdaptor.java:173)<br>
>>> at org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.createContainerEntityManagerFactoryBuilder(PhaseOnePersistenceUnitServiceImpl.java:243)<br>
>>> at org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.access$800(PhaseOnePersistenceUnitServiceImpl.java:60)<br>
>>> at org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl$1$1.run(PhaseOnePersistenceUnitServiceImpl.java:118)<br>
>>> ... 7 more<br>
>>><br>
>>> Clearly it looks like I'm being served classes from the bundled<br>
>>> Hibernate 4.x implementation - on top of those from the module I'm<br>
>>> requesting. This isn't what the deployer should be doing, right?<br>
>>><br>
>>> # Second experiment - use the "application provided"<br>
>>><br>
>>> In this case I hope to hint the JPA deployer to not add the default<br>
>>> implementor but look for a JPA implementation within my deployment,<br>
>>> but still package my custom Hibernate build as a module.<br>
>>><br>
>>> - use the same custom module containing Hibernate ORM 5 (a preview snapshot)<br>
>>> - Add a "Dependency:" section to the manifest to import (and export)<br>
>>> my custom module<br>
>>> - set the "jboss.as.jpa.providerModule" property to value "application"<br>
>>><br>
>>> This gets me:<br>
>>><br>
>>> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:<br>
>>> WFLYJPA0027: Persistence provider module load error application (class<br>
>>> org.hibernate.jpa.HibernatePersistenceProvider)<br>
>>> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.lookupProvider(PersistenceUnitServiceHandler.java:985)<br>
>>> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:267)<br>
>>> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleWarDeployment(PersistenceUnitServiceHandler.java:200)<br>
>>> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:131)<br>
>>> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)<br>
>>> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)<br>
>>> [wildfly-server-1.0.0.CR1.jar:1.0.0.CR1]<br>
>>> ... 5 more<br>
>>> Caused by: org.jboss.modules.ModuleNotFoundException: application:main<br>
>>> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:236)<br>
>>> [jboss-modules.jar:1.4.3.Final]<br>
>>> at org.jboss.as.jpa.persistenceprovider.PersistenceProviderLoader.loadProviderModuleByName(PersistenceProviderLoader.java:65)<br>
>>> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.lookupProvider(PersistenceUnitServiceHandler.java:978)<br>
>>> ... 10 more<br>
>>><br>
>>> Remarks:<br>
>>> - it's attempting to load the "application:main" module?! that's not<br>
>>> what I'd expect from reading [1]<br>
>><br>
>> This seems to be a bug. I hit it a few days ago when I packaged<br>
>> Hibernate ORM 4.1.x with an application (in a unit test) and forgot to<br>
>> set the persistence provider in persistence.xml.<br>
>><br>
>>> - the provider should be available to the deployment classpath, so<br>
>>> I'm not sure why it's not finding the Provider? (I'm even exporting<br>
>>> it, although I'm not sure if that was required).<br>
>><br>
>> Providers are always found through the<br>
>> javax.persistence.spi.PersistenceProviderResolver, not directly from the<br>
>> deployment classpath.<br>
>><br>
>>><br>
>>> Any suggestions to get this running please?<br>
>>><br>
>>> Also I wonder if some of these should warrant opening a JIRA, but I'm<br>
>>> not sure how far I misunderstood the intentions of these JPA deployer<br>
>>> properties.<br>
>><br>
>> Lets talk in a few days again on IRC.<br>
>><br>
>>><br>
>>> Thanks,<br>
>>> Sanne<br>
>>><br>
>>> [1] - <a href="https://docs.jboss.org/author/display/WFLY9/JPA+Reference+Guide#JPAReferenceGuide-Persistenceunitproperties" target="_blank">https://docs.jboss.org/author/display/WFLY9/JPA+Reference+Guide#JPAReferenceGuide-Persistenceunitproperties</a><br>
>> _______________________________________________<br>
>> wildfly-dev mailing list<br>
>> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>