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

Configuring a Relational Aggregate Collection Mapping (ELUG)

Revision as of 08:15, 17 December 2007 by Rick.sapir.oracle.com (Talk | contribs)

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.


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.

This table lists the configurable options for a relational aggregate collection mapping.

Option Workbench Java

Database field

Unsupported

Supported

Reference descriptor

Unsupported

Supported

Container policy

Unsupported

Supported

Method or direct field access

Unsupported

Supported

Read-only mapping

Unsupported

Supported

Batch reading

Unsupported

Supported

Bidirectional relationship

Unsupported

Supported

Query key order

Unsupported

Supported

Configuring Configuring Table and Field References

Unsupported

Supported


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:


Copyright Statement

Back to the top