- Direct Known Subclasses:
- ParsingConfigImpl
public abstract class ParsingConfig
extends java.lang.Object
Parsing config contains information ADFc metadata layer uses to retrieve and parse ADFc resources.
Following settings can be specified:
resourceName name of the metadata resource that is parsed
useCustomizationsindicates whether customizations should be loaded with the base document,
and whether corresponding changes to the metadata resource should be saved as customizations.
It also determines whether ADFc parsers will check for the presence of the root element:
if useCustomizations is false, then it is possible that the root element is missing, because
the document is just being created.
skipIntegrityValidations if true, the Controller will not attempt to validate whether modifications
to this resource preserve its integrity. For example, if integrity validation is skipped, it is
possible to add a control flow rule for which the source or target activities do not exists.
All validations are performed against the document model that existed at the beginning of the request.
This flag should be used so that multiple artifacts can be added to ADFc model in a single request,
such as a view activity and a corresponding control flow rule. This flag does not disable
all of the validation logic, only the logic that depends on the current document context.
pickUpNewResourcesif true, new metadata resources that were created in the current session
will be picked up. This flag is passed directly to the underlying metadata layer.
See MDSSession#getMutableMO(MOReference, boolean)
for details.
mutable indicates whether the requested resource can be modified using DT@RT APIs.
mobile if true, resource represents mobile task flow.
preserveDOM indicates whether DOM Document and Node should be
stored in the parsed model. This option will also skip any metadata caches and retrieve
the document directly from MDS.