Jump to: navigation, search

EclipseLink/UserGuide/JPA/Basic JPA Development/Configuration/JPA/eclipselink-orm.xml

< EclipseLink‎ | UserGuide‎ | JPA‎ | Basic JPA Development‎ | Configuration
Revision as of 09:52, 25 April 2012 by James.sutherland.oracle.com (Talk | contribs) (Specifying EclipseLink Object-Relational Mappings Using eclipselink-orm.xml)

EclipseLink JPA

Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse Source

Specifying EclipseLink Object-Relational Mappings Using eclipselink-orm.xml

You can use EclipseLink’s native metadata XML file, eclipselink-orm.xml, to override mappings defined in JPA’s configuration file orm.xml and to provide extended ORM features.

Elug note icon.png

Note: Using the eclipselink-orm.xml mapping file enables many EclipseLink advanced features, but it may prevent the persistence unit from being portable to other JPA implementations.

The eclipselink-orm.xml file defines object-relational mapping metadata for EclipseLink. It is built from the existing orm.xml file which makes it more intuitive, requires minimum configuration, and makes it easy to override.

Elug javaspec icon.gif

For more information, see Section 12.2 "XML Overriding Rules" in the JPA Specification.

The schema for EclipseLink 2.3 is eclipselink_orm_2_3.xsd.

Overriding and Merging

To override the orm.xml file's mapping, you must define the META-INF/eclipselink-orm.xml file in the project. When both orm.xml and eclipselink-orm.xml are specified, the contents of eclipselink-orm.xml override orm.xml and any other JPA mapping file specified in the persistence unit. If there are overlapping specifications in multiple ORM files, the files are merged if they are no conflicting entities.

See Overriding and Merging Metadata Values for more information.

Version: 2.2.0 DRAFT
Other versions...