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.
Configuring a Relational Aggregate Collection Mapping (ELUG)
This section describes the various components that you must configure in order to use a relational aggregate collection mapping.
Note: To use a relational aggregate collection mapping with Workbench, you must use an amendment method (see Configuring Amendment Methods). |
For information on how to configure EclipseLink mappings options common to two or more mapping types, see Configuring a Mapping.
For information on how to create EclipseLink mappings, see Creating a Mapping.
Configurable Options for Relational Aggregate Collection Mapping lists the configurable options for a relational aggregate collection mapping.
Introduction to Relational Aggregate Collection Mapping Configuration
This table lists the configurable options for a relational aggregate collection mapping.
Configurable Options for Relational Aggregate Collection Mapping
Option | Workbench | Java |
---|---|---|
Database field (see Configuring a Database Field) |
||
Reference descriptor (see Configuring Reference Descriptor) |
||
Container policy (see Configuring Mapping Comments) |
||
Method or direct field access (see Configuring a Type Conversion Converter) |
||
Read-only mapping (see Configuring Read-Only Mappings) |
||
Batch reading (see Configuring Batch Reading) |
||
Bidirectional relationship (see Configuring Bidirectional Relationship) |
||
This example shows how to create a aggregate collection mapping and add it to a descriptor using Java code.
Aggregate Collection Mapping
public void customize(ClassDescriptor descriptor) { AggregateCollectionMapping mapping = new AggregateCollectionMapping(); // configure mapping ... // add mapping to descriptor descriptor.addMapping(mapping); }
For more information, see the following: