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 "Configuring a Relational Aggregate Collection Mapping (ELUG)"

m
m
 
Line 116: Line 116:
  
 
[[Category: EclipseLink User's Guide]]
 
[[Category: EclipseLink User's Guide]]
[[Category: Draft]]
+
[[Category: Release 1]]
 
[[Category: Task]]
 
[[Category: Task]]
 
[[Category: ORM]]
 
[[Category: ORM]]

Latest revision as of 07:35, 20 August 2008

For information on how to create EclipseLink mappings, see Creating a Mapping.


Note: To use a relational aggregate collection mapping with Workbench, you must use an amendment method.


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