CLI Usage
daffodil [GLOBAL_OPTIONS] <subcommand> [SUBCOMMAND_OPTIONS]
Environment Variables
Setting environment variables may be necessary to allow for importing/includes to work and when running tdml files.
DAFFODIL_CLASSPATH
The Daffodil implementation will look on the classpath for includes and imports, and some tdml files. To define additional directories where Daffodil should look for files, set the DAFFODIL_CLASSPATH environment variable, for example:
| Code Block | ||
|---|---|---|
| ||
$ export DAFFODIL_CLASSPATH="/path/to/imports/:/path/to/includes/" |
In addition to defining directories to search for imports and includes, you can add a CatalogManager.properties file to the DAFFODIL_CLASSPATH to direct Daffodil to a relative path location of a user XML Catalog. For information on the CatalogManager.properties file, vist the following website:
http://xerces.apache.org/xml-commons/components/resolver/tips.html#properties
DAFFODIL_JAVA_OPTS
If you need to specify java options specific to Daffodil, you can set the DAFFODIL_JAVA_OPTS environment variable. If not specified, the JAVA_OPTS environment variable will be used. If that is not specified, reasonable defaults for Daffodil will be used.
Global Options
| Long | Short | Description |
|---|---|---|
--debug | -d | Enable the interactive debugger. See the Interactive Debugger documentation for more information. |
--version | -v | Enable verbose output. |
Parse Subcommand
Parse a file, using either a DFDL schema or a saved parser.
Usage
Note that the -P or --parser feature is not yet implemented (April 2013)
...
Unparse an infoset file, using either a DFDL schema or a saved parser.
Usage
Note that the Unparse subcommand is not currently implemented (April 2013).
...
Create a save a parser that can be reused for parsing and unparsing.
Usage
Note that the save-parser command is not currently implemented (April 2013).
...
List or execute tests in a TDML file.
Usage
daffodil test [-t] [-r] <tdmlfile> [<testname>...]
...