Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338246

Summary:	No primary key exception generated when Entity is overriden in the eclipselink-orm.xml
Product:	z_Archived	Reporter:	Karen Butzke <karenfbutzke>
Component:	Eclipselink	Assignee:	Project Inbox <eclipselink.orm-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	tom.ware
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Karen Butzke

2011-02-25 12:11:28 EST

I am testing around with the examples given in:
http://wiki.eclipse.org/EclipseLink/UserGuide/JPA/Basic_JPA_Development/Configuration/JPA/Overriding_and_Merging#Overriding_and_Merging_Examples

For example 4, I set it up so that mapping c is a basic mapping in the orm.xml and a version mapping in the extensions/eclipselink-orm.xml. No exception is generated. If they were both the same mapping type, I get the exception:

Exception Description: Conflicting XML elements [<basic>] with the same name [c] were found. The first was found in the mapping file [file:/C:/Eclipse/runtime-New_configuration/EclipseLinkJpa/build/classes/META-INF/extensions/eclipselink-orm.xml] and the second in the mapping file [file:/C:/Eclipse/runtime-New_configuration/EclipseLinkJpa/build/classes/META-INF/orm.xml]. Named XML elements must be unique across the persistence unit.

Testing using nightly build eclipselink-2.3.0.v20110225-r9029

Comment 1 Tom Ware

2011-03-18 09:32:51 EDT

Setting target and priority.  See the following page for the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines

Community: Please vote for this bug if it is important to you.  Votes are one of the main criteria we use to determine which bugs to fix next.

Comment 2 Eclipse Webmaster

2022-06-09 10:09:34 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink