| Summary: | Multiple Mapping files do not work in one persistence unit | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Gerald <neo79s> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipselink.orm-inbox, guy.pelletier, j.edward.rayl, neo79s, tom.ware | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gerald
You can also get around the issue by removing one of the persistence unit metadata from one of the mapping files as they are the same (you would have seen a conflict exception otherwise had they been different). Typically a persistence unit metadata is only specified in one mapping file but it is valid to have it in multiples, e.g. if you want to seperate Eclipselink specific metadata from JPA metadata into an eclipselink-orm.xml. (an eclipselink-orm.xml also has the power to override as well and avoid conflict exceptions as mentioned previously) Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Created attachment 195126 [details]
Proposed changes
Changes have been submitted. Verified by: Tom Ware Test: Metadata processing error therefore existing XML model modified to expose the exception. With the fix in place, the exception goes away and all tests pass (full regression test suite and extended jpa test suite). The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |