Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] Minutes: Functional Spec Review 200040 - 12/06/2007

Attendees:
Doug Clarke, Shaun Smith, Guy Pelletier, Blaise Doughan, Gordon Yorke, Mike Keith, James Sutherland, Peter Krogh

Action items:

EclipseLinkOrm xml is a compliment to orm.xml but also allows overriding.
	- handle the case where people use two files, encourage the case where they use one file.
Potential overriding within a mapping
	- Should we investigate overiding within a mapping, so that users don't have to redefine full mapping
		- Decided to begin with redefining whole mapping, will potentially look at drilling in later.

Open Issues
6 Should we allow multiple entities to be defined across multiple mapping files. That is, not only in the eclipselink-orm.xml where users can extend their entity definitions from other persistence unit mapping files. 
	- Not going to allow multi definition of Entity across the same type of orm.xml file.
	- Throw an exception if: Same Entity exists in two or more orm.xml or two elorm.xml 
		- investigate if this is straight forward.  Implement if it is.
7 For catalog, schema and access (from entity-mappings which are file defaults) should they apply to overlayed metadata in the eclipselink-orm.xml or apply only to entities with a full definition in the eclipselink-orm.xml file? 
	- Do similar to what we do now

		- applied locally unless they are extensions
		- accessType - special case, ignore what comes from file 
		- catalog, schema - don't override, they apply to this file only
 .



Back to the top