Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/JPA2.0/association-override-join-table"

(Issue Summary)
(General Solution)
Line 12: Line 12:
 
==General Solution==
 
==General Solution==
  
For the most part, the solution for this will mainly be in the metadata processing. However, to support a association override join table from an embeddable class with require some changes to core code, namely AggregateObjectMapping.
+
For the most part, the solution for this will mainly be in the metadata processing. However, to support an association override join table from an embeddable class will require some changes to core code, namely to AggregateObjectMapping.
  
 
== Examples ==
 
== Examples ==

Revision as of 09:23, 2 June 2009

Association Override Join Table support

JPA 2.0 Root | Enhancement Request

Issue Summary

JPA 2.0 specification introduced support for relational mappings such as 1-M, M-M etc on embeddable class. With that comes the option to specify an association override to apply to those mappings within the embeddable, namely those mappings that use a join table. Note an association override can also be specified at the entity level and applied to a mapping from a mapper superclass. This is existing functionality, however with the introduction of the join table element within the association override in JPA 2.0, this support needs to be implemented.

At the same time, changes will be made to support association override join columns on a uni-directional one to many from an embeddable class. Note, that support (although not explicitely supported from the spec in JPA 1.0) for association override join columns to 1-1 and 1-M mappings from an embeddable class was already implemented and tested.

Association overrides are described in detail in section 11.1.2 of the specification.

General Solution

For the most part, the solution for this will mainly be in the metadata processing. However, to support an association override join table from an embeddable class will require some changes to core code, namely to AggregateObjectMapping.

Examples

Annotation - Mapped superclass override


XML - Mapped superclass override


Annotation - Embeddable override


XML - Embeddable override


Work Required

  1. Develop model for testing
    approx 5 day
  2. Update Processing
    approx 10 days

Back to the top