Chunks of data from non-relational data sources can have an
embedded component objects. These can be
mapped using this mapping. The format of the embedded
data is determined by the reference descriptor.

setField(org.eclipse.persistence.internal.helper.DatabaseField field)
The aggregate object is held in a single field.

java.lang.Object

valueFromObject(java.lang.Object object,
org.eclipse.persistence.internal.helper.DatabaseField field,
org.eclipse.persistence.internal.sessions.AbstractSession session)
INTERNAL:
Extract and return value of the field from the object

writeFromObjectIntoRow(java.lang.Object object,
org.eclipse.persistence.internal.sessions.AbstractRecord record,
org.eclipse.persistence.internal.sessions.AbstractSession session)
INTERNAL:
Build the value for the database field and put it in the
specified database row.

writeFromObjectIntoRowWithChangeRecord(org.eclipse.persistence.internal.sessions.ChangeRecord changeRecord,
org.eclipse.persistence.internal.sessions.AbstractRecord row,
org.eclipse.persistence.internal.sessions.AbstractSession session)
INTERNAL:
Get the attribute value from the object and add the appropriate
values to the specified database row.

INTERNAL:
Builds a shallow original object. Only direct attributes and primary
keys are populated. In this way the minimum original required for
instantiating a working copy clone can be built without placing it in
the shared cache (no concern over cycles).

writeFromObjectIntoRowForUpdate

INTERNAL:
If it has changed, build the value for the database field and put it in the
specified database row.
If any part of the aggregate object has changed, the entire object is
written to the database row (i.e. partial updates are not supported).

convertClassNamesToClasses

INTERNAL:
Convert all the class-name-based settings in this mapping to actual class-based
settings. This method is used when converting a project that has been built
with class names to a project with classes.