Migration Glassfish 3.1.2 to Wildfly: Challenge trying to get EclipseLink to Work

[sharkbite]

Hi

I have got EclipseLink enabled on WildFly using post from other forums.

The problem I am getting now is:

10:53:43,430 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("deploy") failed - address: ({"deployment" => "fnds-ear-1.0.0.ear"}) - failure description: {

    "JBAS014671: Failed services" => {"jboss.persistenceunit.\"fnds-ear-1.0.0.ear/fnds-persistence-1.0.0.jar#za.co.fnds_fnds-core_ejb_1.0.0PU\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"fnds-ear-1.0.0.ear/fnds-persistence-1.0.0.jar#za.co.fnds_fnds-core_ejb_1.0.0PU\": javax.persistence.PersistenceException: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.EntityManagerSetupException

Exception Description: Predeployment of PersistenceUnit [za.co.fnds_fnds-core_ejb_1.0.0PU] failed.

Internal Exception: Exception [EclipseLink-7250] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.ValidationException

Exception Description: [class za.co.fnds.persistence.entities.Tcu05CustomerBinProgs] uses a non-entity [class za.co.fnds.persistence.entities.Tca11BinPrograms] as target entity in the relationship attribute [field binProgId].

    Caused by: javax.persistence.PersistenceException: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.EntityManagerSetupException

To make this error go away I add za.co.fnds.persistence.entities.Tca11BinPrograms to the persitance.xml. Please see file attached

How do I solved this problem of not adding all these entities into this xml file? What does it mean when you add them to this file using the class tag?

Tks,

daslan

[jamezp]

Is there something stopping you from using JPA that you need to rely on EclipseLink?

--

James R. Perkins

[sharkbite]

Hi

We are using JPA and using  EclipseLink as the JPA provider.

Also the application was built on Glassfish using JPA with EclipseLink as the provider. First prize will be getting this working as is. Once this is done we will consider using Hibernate by Stressing test our application using both providers.

Tks,

daslan

[jamezp]

If you're using vanilla JPA then the provider shouldn't really matter. Replacing the JPA provider is not really an easy task with any Java EE application server which is why it's always best to write to the API and not the implementation. While I've heard of others getting EclipseLink to work on WildFly I don't know much about it.

If you're just using standard JPA and not relying on anything in EclipseLink I'd encourage you to just try using the provided JPA implementation which in the case of WildFly is Hibernate.

--

James R. Perkins

[sakkie6yster]

Hi Daslan,

This sounds more like an issue with your JPA entities not being automatically detected. To resolve your problem please refer to this JPA Reference Guide that will guide you on how to setup Wildfly 8 with EclipseLink.

It is imperative that you follow all the steps exactly in order to ensure that all known issues regarding EclipseLink on Wildfly 8 is dealt with.

Success

Izaak

[sharkbite]

Thanks Izaak! Went over the guide with a fine comb and saw what I was missing

[skorejo]

Hi, what did you change to make it work?