Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Bug 218084 - XML merging

The work for this feature has now been completed. However another issue came up during testing.

Within our extended tests we have 3 persistence unit (Employee, Relationship and Complex Aggregate). After creating the eclipselink-orm.xml which contained extensions for the Employee persistence unit only, validation exceptions would occur for the other persistence units since they would automatically pick up the eclipselink-orm file (just like an orm.xml file would be).

To get around the problem, I introduced the following property that can be use in the persistence.xml to turn off the automatic discovering of the eclipselink-orm.xml file.
<property name="eclipselink.exclude-eclipselink-orm" value="true"/>

So the question is, do we like this solution?


----- Original Message ----- From: "Guy Pelletier" <guy.pelletier@xxxxxxxxxx> To: "Dev mailing list for Eclipse Persistence Services" <eclipselink-dev@xxxxxxxxxxx>
Sent: Thursday, April 17, 2008 2:17 PM
Subject: [eclipselink-dev] Bug 218084

Work is about to begin to resolve bug 218084 - Implement metadata merging functionality between mapping files

As of now, the implementation will align with the details provided in the functional spec:

Therefore, this is a last call for feedback. The implementation of this feature is slated to begin on Monday, April 21st assuming there are no major issues raised in the feedback.

Please provide any comments you may have about this feature in the bug:


eclipselink-dev mailing list

Back to the top