Community
Participate
Working Groups
Currently in "websphere-install" target in jpa/eclipselink.jpa.test/websphere.xml, we copy eclipselink.jar to WAS_INSTALL/lib/ext as a workaround fix for bug 268219, then the xdb.jar which is needed for customfeatures model can't be loaded from "compile.server.path". In order to solve this, we can copy xdb.jar to WAS_INSTALL/lib/ext, then xmlparserv2.jar needs to be copied to the same dir, but this will result in failure of start websphere server(verified on WAS7) with xmlparserv2.jar under WAS_INSTALL/lib/ext, so this workaround is not valid. So with this situation, the nightly test result for customfeatures model doesn't reflect the real error as described in bug 269561. We can only manually run this model by removing eclipselink.jar from WAS_INSTALL/lib/ext to get real error.
The fix has been checked in Main as revision 5955, 1.2.X as revision 5957 and 1.1.X as 5960: 1. add xdb.jar and xmlparserv2.jar entries in configWebSphere.py when configuring shared library on WebSphere 2. modify websphere.properties by adding oracle.extensions.jar.dir=/scratch/aime/eclipselink/org.eclipse.persistence/extension.oracle.lib.external, since WebSphere needs absolute dir when configuring shared library 3. modify websphere.xml by adding <replace file="${was.home}/bin/configWebSphere.py" token="%%oracleExtensionLibDir%%" value="${oracle.extensions.jar.dir}"/> to get real oracle extension lib directory. code is reviewed by Kevin Yuan.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
