1. Overview of Oracle GlassFish Server 3.1 Application Deployment
A. The asadmin Deployment Subcommands
B. GlassFish Server Deployment Descriptor Files
C. Elements of the GlassFish Server Deployment Descriptors
activation-config-property-name
activation-config-property-value
check-version-of-accessed-instances
Specifies the fetch group configuration for fields and relationships. The fetched-with element has different allowed and default subelements based on its parent element and the data types of the fields.
If there is no fetched-with subelement of a cmp-field-mapping, and the data type is not BLOB, CLOB, VARBINARY, LONGVARBINARY, or OTHER, fetched-with can have any valid subelement. The default subelement is as follows:
<fetched-with><default/></fetched-with>
If there is no fetched-with subelement of a cmp-field-mapping, and the data type is BLOB, CLOB, VARBINARY, LONGVARBINARY, or OTHER, fetched-with can have any valid subelement except <default/>. The default subelement is as follows:
<fetched-with><none/></fetched-with>
If there is no fetched-with subelement of a cmr-field-mapping, fetched-with can have any valid subelement. The default subelement is as follows:
<fetched-with><none/></fetched-with>
Managed fields are multiple CMP or CMR fields that are mapped to the same column. A managed field can have any fetched-with subelement except <default/>. For additional information, see Managed Fields in Oracle GlassFish Server 3.1 Application Development Guide.
cmp-field-mapping, cmr-field-mapping (sun-cmp-mappings.xml)
The following table describes subelements for the fetched-with element.
Table C-58 fetched-with Subelements
|