Re: Re: [Fwd: EclipseLink2 BROKEN on JOnAS 5.2.0 RELEASE ?]
"Hans J. Prueller" <[email protected]> Fri, 15 Apr 2011 07:51:52 +0200
| Newsgroups | gmane.comp.java.objectweb.jonas |
|---|---|
| Organization | LBS logics GmbH |
| Message-ID | <1302846712.2134.14.camel@kodos> |
Hi Florent, meanwhile I had time to perform the test you suggested - I replaced the EasyBeans core bundle of 5.2.0 (release) with the EasyBeans core bundle of my working 5.2.0 M5 installation. Now deployment of the application (EAR) works perfectly, also persistence with EclipseLink2 works without problems again. Seems that some change in EasyBeans core between 5.2.0 M5 and 5.2.0 release broke "weaving" ? regards, HANS Am Montag, den 11.04.2011, 09:59 +0200 schrieb Florent BENOIT: > Hi Hans, > > We didn't change the EclipseLink version between JOnAS 5.2.0 M5 and > 5.2.0 version (EclipseLink 2.1.2) > > I also found several similag bugs in the EclipseLink2 Issue tracker : > https://bugs.eclipse.org/bugs/show_bug.cgi?id=322679 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403 > > Looks like the weaving didn't occur. > https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403#c9 > > Also, for a test, could you replace the EasyBeans core bundle 5.2.0 > and replace it with the bundle of 5.2.0-M5 : > JONAS_ROOT/repositories/maven2-internal/org/ow2/easybeans/osgi/easybeans-modules-core/ > > Regards, > > Florent > > > > Hans J. Prueller wrote: > > > hi all, > > > > had anyone a look at this - upgraded 5.2.0-RC to 5.2.0-release with > > identical sourcecode/ear package and > > deployment fails with error message below ... ? > > > > hans > > > > > > -------- Weitergeleitete Nachricht -------- > > Von: Hans J. Prueller <[email protected]> > > Reply-to: [email protected] > > An: [email protected] > > Betreff: [jonas] EclipseLink2 BROKEN on JOnAS 5.2.0 RELEASE ? > > Datum: Thu, 07 Apr 2011 08:02:10 +0200 > > > > Hi All, > > > > I guess something is broken with EclipseLink2 on JOnAS 5.2.0 Release > > Version. > > > > We switchted to EclipseLink2 without Problems - it worked fine > > until 5.2.0-M5. > > > > Now when I try to upgrade my development machine to 5.2.0 release > > version, I get the following error: > > > > ***** > > > > [EL Info]: 2011-04-07 > > 07:57:50.073--ServerSession(297333178)--EclipseLink, version: > > Eclipse Persistence Services - 2.1.2.v20101206-r8635 > > [EL Info]: 2011-04-07 > > 07:57:50.148--ServerSession(297333178)--Server: EasyBeans > > [EL Severe]: 2011-04-07 > > 07:57:50.652--ServerSession(297333178)--Local Exception Stack: > > Exception [EclipseLink-0] (Eclipse Persistence Services - > > 2.1.2.v20101206-r8635): > > org.eclipse.persistence.exceptions.IntegrityException > > Descriptor Exceptions: > > --------------------------------------------------------- > > > > Exception [EclipseLink-60] (Eclipse Persistence Services - > > 2.1.2.v20101206-r8635): > > org.eclipse.persistence.exceptions.DescriptorException > > Exception Description: The method > > [_persistence_set_businessTripDay_vh] or > > [_persistence_get_businessTripDay_vh] is not defined in the object > > [com.lbslogics.ims.model.Event]. > > Internal Exception: java.lang.NoSuchMethodException: > > com.lbslogics.ims.model.Event._persistence_get_businessTripDay_vh() > > Mapping: > > org.eclipse.persistence.mappings.ManyToOneMapping[businessTripDay] > > Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event --> > > [DatabaseTable(EventBean_)]) > > > > Exception [EclipseLink-60] (Eclipse Persistence Services - > > 2.1.2.v20101206-r8635): > > org.eclipse.persistence.exceptions.DescriptorException > > Exception Description: The method [_persistence_set_businessTrip_vh] > > or [_persistence_get_businessTrip_vh] is not defined in the object > > [com.lbslogics.ims.model.Event]. > > Internal Exception: java.lang.NoSuchMethodException: > > com.lbslogics.ims.model.Event._persistence_get_businessTrip_vh() > > Mapping: > > org.eclipse.persistence.mappings.ManyToOneMapping[businessTrip] > > Descriptor: RelationalDescriptor(com.lbslogics.ims.model.Event --> > > [DatabaseTable(EventBean_)]) > > > > Runtime Exceptions: > > --------------------------------------------------------- > > > > java.lang.NullPointerException > > > > at > > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:471) > > at > > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.initializeDescriptors(DatabaseSessionImpl.java:406) > > at > > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:666) > > at > > org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:615) > > at > > org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:228) > > at > > org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:389) > > at > > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:164) > > at > > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:221) > > at > > org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:209) > > at > > org.ow2.easybeans.persistence.TxEntityManagerHandler.buildNewTxEntityManager(TxEntityManagerHandler.java:124) > > at > > org.ow2.easybeans.persistence.TxEntityManagerHandler.getCurrent(TxEntityManagerHandler.java:112) > > at > > org.ow2.easybeans.persistence.TxEntityManager.getCurrentEntityManager(TxEntityManager.java:74) > > at > > org.ow2.easybeans.persistence.TxEntityManager.createNamedQuery(TxEntityManager.java:246) > > at > > org.ow2.easybeans.persistence.ContainerManagedEntityManager.createNamedQuery(ContainerManagedEntityManager.java:244) > > at > > com.lbslogics.ims.model.Employee.findByAppUsername(Employee.java:192) > > > > ***** > > > > > > We did not change a single line of code which basically works > > perfect on JOnAS 5.2.0-M5 with eclipselink2 ---> guess it is some > > configuration > > problem of the 5.2.0 release bundle ??? > > > > > > Hans > > > >