10:59 a.m.
[
https://issues.jboss.org/browse/WFLY-9053?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on WFLY-9053:
---------------------------------------
[~heruan] the version change I applied has some additional consequences, in particular it
now pulls in the JipiJapa integration from WF11. Previously it would bundle the
integration component meant for WF10, which was causing the exception you described.
[~andrei.ivanov] excellent question: this has been a very hard choice indeed. The WildFly
project is very strict about backwards compatibility, but in the update of Hibernate ORM
from 5.1 to 5.2 we had to break one single method's signature.
This change was essential for us (Hibernate team) as we're working on long term
improvements and paving the road for very nice improvements in ORM 6, so after much debate
we decided that breaking one single method was a reasonable compromise for our users.
Since we understand it's not acceptable for everyone, we'll be maintaining 5.1 as
well. You can effectively think 5.2 as a stepping stone in preparation for 6.
The "deal breaker" change can be found here:
https://github.com/hibernate/hibernate-orm/wiki/Migration-Guide---5.2 Search for
{{getFlushMode}}.
There are often many more changes of course, but this one affects public API and we
believe it might be used quite frequently.
AbstractMethodError with Hibernate 5.2
--------------------------------------
Key: WFLY-9053
URL: https://issues.jboss.org/browse/WFLY-9053
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Giovanni Lovato
Assignee: Scott Marlow
I'm deploying an EAR specifying in its {{persistence.xml}} to use Hibernate 5.2 as
JPA provider:
{code:xml}
<property name="jboss.as.jpa.providerModule"
value="org.hibernate:5.2" />
{code}
Hibernate 5.2 modules are placed in the {{modules}} directory.
This configuration works in 10.1.0.Final but in 11.0.0.Alpha1 I get this error at
deployment:
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start
service jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE:
WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment
"oss-application-ear-1.0.0.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.AbstractMethodError:
org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.beanManagerLifeCycle(Ljavax/enterprise/inject/spi/BeanManager;)Ljava/lang/Object;
at
org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.<init>(PhaseOnePersistenceUnitServiceImpl.java:89)
at
org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:485)
at
org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:279)
at
org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
at
org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
at
org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
2439
days inactive
2439
days old
0 comments
1 participants
participants (1)
-
Sanne Grinovero (JIRA)