Community
Participate
Working Groups
Currently, orm mapping files do not merge their metadata with other mapping files. That is, entity, embeddable etc. definitions are assumed to be fully defined within a mapping file. If an entity is defined in multiple files, results are unexpected as a 'last in win' approach is currently in place.
See the functional spec for the details of this feature. http://wiki.eclipse.org/EclipseLink/Development/200040/FunctionalSpec#Override_and_Merging_Rules
Created attachment 100683 [details] Proposed patch
Created attachment 100706 [details] Updated patch
Created attachment 101074 [details] Final patch
The patch has been submitted. Reviewed by: Tom Ware No new tests were added. However, the existing xml extended advanced model was modified to include an eclipselink-orm.xml file with the extended mappings for that model. Hence reverting the advanced-extended-entity-mappings.xml for that model back to its original JPA format. All tests (JPA and extended) should continue to pass without any errors.
(In reply to comment #5) Should this be documented in EclipseLink Dev. Guide?
Yes. I have entered a new bug 234914 for this.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink