Community
Participate
Working Groups
Created attachment 151277 [details] Build artifacts for NetWeaver server tests The server platform for the SAP NetWeaver 7.1 application server is currently available in the incubator (see bug 287167). The attached patch contains the build artifacts (netweaver.xml, netweaver.properties and additional resources) that are required to execute the JPA server tests on the NetWeaver platform. With these changes applied it is technically possible to execute the tests inside NetWeaver. (The current situation is that many of the tests still fail but that will be investigated separately.) Would it be possible to add the NetWeaver build files to the JPA test project although the NetWeaver platform is still in the incubator?
I can see no issue with adding these files since they will have no effect on non-netweaver users. Perhaps this is a good task for the new SAP committers.
Created attachment 154963 [details] build files as provided by Sabine but taking additionally packaging build result from netweaver server platform incubator To execute the server tests on NetWeaver, an application archive "servertest_eclipselink.ear" is created and deployed, which contains EclipseLink, the build result from the NetWeaver server platform extension, and junit 4.5. The application under test "servertest.ear" has a classloader reference to "servertest_eclipselink.ear". JPA 2.0 API and validation.jar are not packaged as NetWeaver 7.1 supports JPA 1.0 only, at the time being.
reviewed by Yiping (asserting that the changes don't affect existing server platforms) checked in at rev 6265
Updated IP Log: http://wiki.eclipse.org/EclipseLink/IPLog#2.1_Contributions
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
