getCompatibilityInstance()
If a Compatibility instance is associated with the Specification,
we will configure this Compatibility instance instead of instantiating a
new one so that the compatibility flags set in compliance with the
Specification can be preserved.

setSpecification

Set the Specification for this configuration.
Specification determines various default properties and behavior.
For example, compatibility options during runtime.
This change will trigger all registered Product Derivations to mutate
other configuration properties.

getDataCacheManagerInstance

The data cache manager manages this configuration's cache instances.
The cache manager is created if it has not been set. Once the cache
manager has been set/created, all changes to caching configuration
must proceed through the cache manager.

getRefreshFromDataCache

Gets whether entity state is to be refreshed from DataCache.
The entities are never refreshed from DataCache if lock is being applied
(e.g. in a pessimistic transaction) and hence this setting only refers
to behavior when not locking.
This flag can be used to overwrite RetrieveMode.BYPASS.
By default, however, this falg is false.

setRefreshFromDataCache

Sets whether entity state is to be refreshed from DataCache.
The entities are never refreshed from DataCache if lock is being applied
(e.g. in a pessimistic transaction) and hence this setting only refers
to behavior when not locking.

setRefreshFromDataCache

Sets whether entity state is to be refreshed from DataCache.
The entities are never refreshed from DataCache if lock is being applied
(e.g. in a pessimistic transaction) and hence this setting only refers
to behavior when not locking.

setConnectionRetainMode

Specifies the behavior of the broker with respect to data store
connections. Possible values are:

always: Each broker obtains a single connection and
uses it until the broker is closed.

transaction: A connection is obtained when each
transaction begins (optimistic or datastore), and is released
when the transaction completes.

on-demand: Connections are obtained only when needed.
This is the default mode. It is equivalent to the previous option
when datastore transactions are used. For optimistic transactions,
though, it means that a connection will be retained only for
the duration of the data store commit process.

getConnectionRetainMode

Specifies the behavior of the broker with respect to data store
connections. Possible values are:

always: Each broker obtains a single connection and
uses it until the broker is closed.

transaction: A connection is obtained when each
transaction begins (optimistic or datastore), and is released
when the transaction completes.

on-demand: Connections are obtained only when needed.
This is the default mode. It is equivalent to the previous option
when datastore transactions are used. For optimistic transactions,
though, it means that a connection will be retained only for
the duration of the data store commit process.

setRetryClassRegistration

Whether to warn and defer registration instead of throwing an
exception when a registered persistent class cannot be processed.
Should only be set to true in complex classloader topologies.
Defaults to false.

getRetryClassRegistration

Whether to warn and defer registration instead of throwing an
exception when a registered persistent class cannot be processed.
Should only be set to true in complex classloader topologies.
Defaults to false.

getCompatibilityInstance

If a Compatibility instance is associated with the Specification,
we will configure this Compatibility instance instead of instantiating a
new one so that the compatibility flags set in compliance with the
Specification can be preserved.

getRuntimeUnenhancedClasses

supported: Runtime optimization of persistent types
is available. This is the default

unsupported: Runtime optimization of persistent types
is not available. An exception will be thrown if the system loads with
persistent types that are not enhanced.

warn: Runtime optimization of persistent types is
not available, but no exception will be thrown initially. A warning will
be logged instead. It is likely that the system will fail at a later
point. This might be suitable for environments with complex classloader
configurations.