Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Below is the list of tunable parameters and their default values:

generatedNamespacePrefixStem"tns"If elementFormDefault is qualified, but no prefix is associated with the targetNamespace, a prefix will be created using this value, with numbers appended if necessary to ensure uniqueness.

In certain I/O optimized situations (text-only, encodingErrorPolicy='replace', fixed-width encoding) input files larger than this will be mmapped. Input files smaller than this will be simply read using ordinary I/O (because for small files that is just faster). This exists because mmap is more expensive than ordinary I/O for small files.

maxBinaryDecimalVirtualPoint200An upper limit on the value of the dfdl:binaryDecimalVirtualPoint property.
220A maximum limit for various daffodil I/O properties, including the maximim size of a simple element and maximum regular expression characters to match.

When unexpected text is found where a delimiter is expected, this is the maximum number of bytes (characters) to display when the expected delimiter is a variable length delimiter.

A maximum limit for the number of repeats of array elements.
maxSkipLengthInBytes1024A maximum limit for the number of bytes that can be skipped in a skip region.


A lower limit on the value of the dfdl:binaryDecimalVirtualPoint property.

Whether to compile a schema to support parsing ("parseOnly"), unparsing ("unparseOnly"), both parsing and unparsing ("both"), or to use the daf:parseUnparsePolicy property from the root node ("schema").


If true, require that the bitOrder property is specified. If false, use a default value for bitOrder if not defined in a schema.


If true, require that the encodingErrorPolicy property is specified. If false, use a default value if not defined in a schema.


Specified how unqualified path steps are resolved. Value values are:


Unqualified path steps remain unqualified and will only match elements in NoNamespace. A prefix must be provided to match namespaced elements.


Unqualified path steps will always use the default namespace. If a default namespace is defined, it is not possible to match a NoNamespace element with this policy. Because of this, this may not work well with elementFormDefault="unqualified".


Attempt to use the default namespace to resolve an unqualified path step. If that fails to match an element, then try to resolve using NoNamespace.

Configuration Schema

The schema for the configuration file is defined in dafext.xsd.