- This topic has 4 replies, 2 voices, and was last updated 13 years, 1 month ago by
.
-
Posts
-
Running WebLogic 10.3.5, EclipseLink 2.1.1, MySQL. When the EntityManager logs in, the log outputs:
INFO: EclipseLink, version: Eclipse Persistence Services – 2.1.3.v20110304-r9073
I have no idea where it’s getting this from. I’ve never downloaded 2.1.3, and am using the default MyEclipse Bling (9.1-Blue-20110701) Eclipse 2.1.x configuration.
When I use Tomcat 6.x with the same EclipseLink / MySQL configuration, the log statement shows the correct version.
The ultimate downstream problem this (seems) to cause is that the first insert fails because the PK column is null. I verifed the PK is set, and is still set in the merged entity. The failure occurs on commit.
LMCO-18,
The MyEclipse eclipselink libraries are for 2.1.1 (though there are earlier ones also available). Is it possible that Weblogic comes with 2.1.3?
Can you describe how you added the eclipselink jar files to your project?
Can you also check if the eclipselink jar files get deployed with your project?
LMCO-18,
I just checked the WebLogic installation. The EclipseLink jar can be found here, within your WebLogic installation directory:
methods\org.eclipse.persistence_1.1.0.0_2-1.jar
If you look inside the META-INF/MANIFEST.MF file within that jar, it shows a 2.1.3 implementation. So I suggest you replace that jar with a 2.1.1 implementation or else ensure that the 2.1.1 jar file is deployed as part of your application as that should take precedence.
Please let us know if this works for you.
Looks like the real problem is that WebLogic doesn’t like non Entity classes in the middle of an Entity class hierarchy. I was able to get it working by removing the non-entity class from the hierarchy.
The non-Entity class was only used to logically group Entity classes so instanceof checks could be performed. It had no data or methods, so I just made it an interface instead.
