Netweaver's ORM library and JPA implementation. How to use EclipseLink?

[Former Member]

Hi,

I'm migrating from Glassfish to Netweaver and when I deploy my EAR on Netweaver I'm receiving the following exception. I have two questions. 1) TABLE_PER_CLASS is supported in EclipseLink but for some reason Netweaver isn't using it as the JPA implementation. Why? 2) What is the com.sap.engine.services.orpersistence.model.ormappingmodel package and how do I avoid using it because it seems to be reading my annotations when I just want it to ignore it and let EclipseLink handle things?

I'm using Netweaver Composition Environment 7.1 and found this little FAQ on the topic:

https://wiki.sdn.sap.com/wiki/display/Java/JavaEE5+FAQ#JavaEE5FAQ-1.190

It says:

Can I use another JPA implementation on top of Java EE 5 Edition?

By design this feature is supported, however it has not been tested in this release. For future releases it is planned to test the SAP NetWeaver AS Java with other available JPA providers.

Not even sure if it's applicable here since the FAQ entry isn't related to CE.

Description:

1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for JavaEE/calendar-ear application.

ERRORS:

• Model Creator: Error during model creation occured: com.sap.engine.services.orpersistence.model.ormappingmodel.ORMException: Unsupported inheritance strategy TABLE_PER_CLASS

at com.sap.engine.services.orpersistence.model.ormappingmodel.impl.ORMUtils.getInheritanceStrategy(ORMUtils.java:1252)

at com.sap.engine.services.orpersistence.model.ormappingmodel.impl.ORMappingModelCreatorImpl.parsePersistentClass(ORMappingModelCreatorImpl.java:831)

Thanks, any help is appreciated.

Edited by: Zarar Siddiqi on Jul 24, 2009 5:32 PM

[Former Member]

I should add that I've gone through the steps outlined in this article:

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60642a88-95fe-2b10-d387-a245d48f...

I've properly configured a Heavy Resource and tested it through telnet so I know its installed properly. However, I still get the same exception. In my persistence.xml I've specified EclipseLink as the persistence provider:

<persistence-unit name="mainDatabase">

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

<jta-data-source>jdbc/Main</jta-data-source>

I'm wondering what I'm missing because Netweaver is still using SAP JPA and not EclipseLink.

Thanks.

[adrian_goerler]

Hi,

this is a known issue. Erroneously, SAP JPA validations are performed although a 3rd party persistence provider is specified.

Fortunately, this issue has already been solved. A patch is available with NW 7.10 SP 7. Please see OSS note 1284984

for details.

-Adrian