Hi Have a look to http://tomee-openejb.979440.n4.nabble.com/CDI-issues-tomee-7-0-2-td4680584.html
Short summary is jpa and cdi have now a chicken egg issue. Most jpa providers solve it being lazy but not hibernate. Wildfly has some hacks like tomee ones - even if different - but we dont avtivate them by default for backward compability - would break older hibernate usage very hard. Le 29 janv. 2017 22:25, "arnieAustin" <[email protected]> a écrit : I have been fighting for hours trying to get an application that worked fine on WildFly to just deploy on TomEE. After much pain, I've come to yet another hard stop as shown in the errors below. The messages coming back from OpenEJB are INCREDIBLY AND DISAPPOINTINGLY VAGUE. What is meant by them is unclear. The only initial hint is: But WHY? What is the exception from Hibernate or JPA that is the actual error? There is nothing here to help. I did find mention of this: but after putting that in the persistence.xml file, completely different errors come to the surface. -- View this message in context: http://tomee-openejb.979440. n4.nabble.com/Migrating-JBoss-CDI-Hibernate-app-to-TomEE- Could-not-access-BeanManager-ListenerFactory-class-tp4680977.html Sent from the TomEE Users mailing list archive at Nabble.com.
