Skip to main content
Jump to: navigation, search

Difference between revisions of "Dali Project/specs/3.0/2.0ElementCollection"

(Requirements / Functionality)
(Requirements / Functionality)
Line 66: Line 66:
  
  
=== Element Collection Map Basic Types===
+
=== Element Collection Map Basic Types ===
 +
* target-class
 +
* fetch - defaults to Lazy
 +
* collection-table and @Collection Table
 +
** Name defaults to <Entity name>_<attribute name>
 
* column and @Column
 
* column and @Column
 
* map-key-column and @MapKeyColumn  
 
* map-key-column and @MapKeyColumn  
Line 72: Line 76:
 
* map-key-enumerated and @MapKeyEnumerated
 
* map-key-enumerated and @MapKeyEnumerated
 
* map-key-convert and @MapKeyConvert
 
* map-key-convert and @MapKeyConvert
* Fetch - defaults to Lazy
+
* map-key-class and @MapKeyClass
* collection-table and @Collection Table
+
* map-key and @MapKey - this and MapKeyClass are mutually exclusive
** Name defaults to <Entity name>_<attribute name>
+
* Validation errors:
 
+
** MapKey and MapKeyClass are both specified
 +
**
  
 
'''Element Collection Map with Basic Key and Basic Value Details'''
 
'''Element Collection Map with Basic Key and Basic Value Details'''

Revision as of 16:14, 14 December 2009

Functional Specification: Dali Support for JPA 2.0 Element Collection mapping

Feedback

bug 258490 - element collection support


Document History

Date Author Version Description & Notes
12-9-2009 Karen Butzke Draft

Project overview

This feature covers the element collection mapping in the JPA 2.0 spec as well as any EclipseLink extensions.

Goals:

  • Add Generic 2.0 support for Element Collection
  • Add EclipseLink 3.0 support for Element Collection with relevant extensions
  • Provide the appropriate defaults and validation for these settings

Concepts

Present any concepts relevant to the feature.

EclipseLink Element Collection Functional Spec

Requirements / Functionality

Element Collection with Basic Type

  • Target Class - defaults to type of the Collection if it is generic
  • Fetch - defaults to Lazy
  • Collection Table
    • Name defaults to <Entity name>_<attribute name>
  • Column
    • Name default to attribute name
    • Table defaults to collection table name and is not editable


Element Collection Basic Type Details

ElementCollectionBasicType.jpg


Ordering Section

Ordering.jpg

Element Collection with Embeddable Type

  • Attribute and Association override names are derived from the Embeddable type


Element Collection Embeddable Type Details

ElementCollectionEmbeddableType.jpg


Element Collection Map Basic Types

  • target-class
  • fetch - defaults to Lazy
  • collection-table and @Collection Table
    • Name defaults to <Entity name>_<attribute name>
  • column and @Column
  • map-key-column and @MapKeyColumn
  • map-key-temporal and @MapKeyTemporal
  • map-key-enumerated and @MapKeyEnumerated
  • map-key-convert and @MapKeyConvert
  • map-key-class and @MapKeyClass
  • map-key and @MapKey - this and MapKeyClass are mutually exclusive
  • Validation errors:
    • MapKey and MapKeyClass are both specified

Element Collection Map with Basic Key and Basic Value Details

ElementCollectionMapBasicKeyAndValue.jpg

Element Collection Map Embeddable Key

  • Overrides
    • In Xml use map-key-attribute-override and map-key-association-override
    • In Java use AttributeOverride(name="key.<name>") and AttributeOverride(name="value.<name>)


File:ElementCollectionMapEmbeddableKeyAndBasicValue.jpg

Element Collection Map Entity Key

  • MapKeyJoinColumn
  • MapKeyJoinColumns

ElementCollectionMapEntityKeyAndBasicValue.jpg

API

Issues

This section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.

Issue # Owner Description / Notes Decision

Future Considerations

During the research for this project the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.

Back to the top