EclipseLink/Development/Incubator/Extensions/NetWeaverPlatform

Note: This page describes an extension of EclipseLink that is part of the EclipseLink incubator. Incubator projects are published so the community can use them either to progress towards having them included in the main product, or to use in their own implementations. They have been tested to varying levels and as such, we recommend doing your own testing before including any of this code in a production-level product. Please report any issues via the bug listed below:

Bug

bug 287167

Description

This is a subclass of ServerPlatform that can be used by customes using the NetWeaver application server.

Note: This project contains 2 new classes and a patch that should be applied to existing classes to integrate these classes into EclipseLink's configuration and logging.

Documentation

Supported Versions

The NetWeaver server platform allows using EclipseLink within an SAP NetWeaver Application Server Java. The following versions are supported:

• SAP NetWeaver 7.1 including EHP 1
• SAP NetWeaver 7.2
• SAP NetWeaver 7.3 (not yet publicly available)

Building the NetWeaver Platform

As a prerequisite, you must have checked out the EclipseLink sources from the trunk branch and performed a successful ant-based build. See EclipseLink/Building for detailed instructions. You should then:

1. Checkout the NetWeaver Platform extension from the location given below.
2. Edit the build.properties file in the checked out sources so that the property trunk.dir points to the root of the EclipseLink source tree (trunk).
3. Call ant.

As a result, you should get a file called netweaver_platform.jar, which you can place alongside with the standard eclipselink.jar.

Using the NetWeaver Platform

The recommended deployment option is to create a separate deployable application (i.e. an SDA file) containing both the eclipselink.jar and the netweaver_platform.jar and to reference that application from your Java EE application. See the NetWeaver Help Portal for a description how to do this using SAP NetWeaver Developer Studio.

Edit the persistence.xml file:

• Add a <provider> tag to each of the defined persistence units (must be the first line after the <persistence-unit> tag) so that EclipseLink will be used as the JPA provider for the respective persistence unit:

<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>

• Include the following property at the end of each persistence unit so that EclipseLink will make use of the NetWeaver platform:

<properties>
  <property name="eclipselink.target-server" value="org.eclipse.persistence.extensions.platform.server.SAPNetWeaver_7_1_Platform"/>   
</properties>

Limitations

• SAP NetWeaver AS Java (version 7.1 to 7.3) is a Java EE 5 server, hence supporting only JPA 1.0.
• Dynamic weaving cannot be used inside SAP NetWeaver AS Java. Applications should use static weaving instead.

Location

svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/incubator/extensions/trunk/org.eclipse.persistence.platform.server.netweaver

Level of Testing

• Sept 3, 2009 - Initial check-in, compile only. Changes to existing EclipseLink classes not integrated.
• Dec 22, 2009 - EclipseLink server tests from trunk (2.1 stream) pass on SAP NetWeaver 7.1, ehp 3 with the following exceptions:

  * Criteria tests should not be executed as the SAP NetWeaver server supports JPA 1.0 only: https://bugs.eclipse.org/bugs/show_bug.cgi?id=298407
  * Test .../advanced/EntityManagerJUnitTestSuite.testSetRollbackOnly fails due to https://bugs.eclipse.org/bugs/show_bug.cgi?id=297558

Location of tests and examples

No specific tests or examples have been written