sapi

Provides the classes necessary to compile DFDL schemas, parse and unparse files using the compiled objects, and retrieve results and parsing diagnostics

Overview

The main class to use is Daffodil to create a Compiler:

val c = Daffodil.compiler()

This can then be used to compiled a DFDL schema, and generate a ProcessorFactory:

val pf = c.compileFile(file)

This can then be used to create a DataProcessor:

val dp = pf.onPath("/")

This can then be used to parse data, returning a ParseResult, which contains the DFDL infoset in either a jdom2 Document or a scala XML Node:

val pr = dp.parse(data)
val infoset = pr.result()

The DataProcessor.parse(java.nio.channels.ReadableByteChannel) method may be called multiple times without the need to create another data processors. For example:

files.foreach { f => {
  val pr = dp.parse(f)
  val infoset = pr.result()
}}

Failures & Diagnostics

It is possible that failures could occur during the creation of the ProcessorFactory, DataProcessor, or ParseResult. However, rather than throwing an exception on error (e.g. invalid DFDL schema, parse error, etc), these classes extend WithDiagnostics, which is used to determine if an error occured, and any diagnostic information (see Diagnostic) related to the step. thus, before contining, one must check WithDiagnostics#isError. For example:

val pf = c.compile(file)
if (pf.isError()) {
  val diags = pf.getDiagnostics()
  diags.foreach { d =>
    System.out.println(d.toString())
  }
  return -1;
}

Saving & Reloading Parsers

In some cases, it may be beneficial to save a parser and reload it. For example, when starting up, it may be quicker to reload an already compiled parser than to compile it from scratch. To save a DataProcessor:

val dp = pf.onPath("/")
dp.save(saveFile);

And to restore a saved DataProcessor:

val dp = Daffodil.reload(saveFile);
val pr = dp.parse(data);

Linear Supertypes

AnyRef, Any

Type Members

class Compiler extends AnyRef

Compile DFDL schemas into ProcessorFactory's or reload saved parsers into DataProcessor's.
class DataLocation extends AnyRef

Information related to a location in data
class DataProcessor extends WithDiagnostics

Compiled version of a DFDL Schema, used to parse data and get the DFDL infoset
class Diagnostic extends AnyRef

Class containing diagnostic information
class InvalidParserException extends Exception

This exception will be thrown as a result of attempting to reload a saved parser that is invalid (not a parser file, corrupt, etc.) or is not in the GZIP format.
class InvalidUsageException extends Exception

This exception will be thrown as a result of an invalid usage of the Daffodil API
class LocationInSchemaFile extends AnyRef

Information related to locations in DFDL schema files
class ParseResult extends WithDiagnostics

Result of calling long), containing the resulting infoset, any diagnostic information, and the final data location
class ProcessorFactory extends WithDiagnostics

Factory to create DataProcessor's, used for parsing data
abstract class WithDiagnostics extends AnyRef

Abstract class that adds diagnostic information to classes that extend it.
Abstract class that adds diagnostic information to classes that extend it.
When a function returns a class that extend this, one should call WithDiagnostics#isError or WithDiagnostics#canProceed on that class before performing any further actions. If an error exists, any use of that class, aside from those functions in WithDiagnostics, is invalid and will result in an Exception.

Value Members

object Daffodil

Factory object to create a Compiler and set global configurations
object ValidationMode extends Enumeration

Validation modes for validating the resulting infoset against the DFDL schema
package debugger

Provides the classes necessary to perform parse tracing or create a custom debugger
Provides the classes necessary to perform parse tracing or create a custom debugger
Overview
Daffodil comes with one prebuilt debugger, the TraceDebuggerRunner, which outputs verbose information during the parsing processes, which can be used to aid in debugging a DFDL schema. For example, the TraceDebuggerRunner can be use like so:
```
val tdr = new TraceDebuggerRunner()
Daffodil.setDebugger(tdr)
```
Additionally, one may create their own debugger runner by implementing the methods in the DebuggerRunner.
Once the debugger is set, it must then be turned on, like so:
```
Daffodil.setDebugging(true);
```
package logger

Provides the classes necessary to recieve logging messages from Daffodil.
Provides the classes necessary to recieve logging messages from Daffodil.
Overview
Daffodil comes with three prebuilt log writers:
- ConsoleLogWriter - writes all log messages to stdout
- FileLogWriter - writes all log messages to file
- NullLogWriter - drop all log messages
To use one of these log writers, create and instance of it and pass it to Daffodil.setLogWriter. For example, to write all logs to /var/log/daffodil.log:
```
val lw = new FileLogWriter(new File("/var/log/daffodil.log"))
Daffodil.setLogWriter(lw)
```
One may also change the log level using Daffodil.setLoggingLevel, which defaults to LogLevel#Info if not set. For example, to change the log level to LogLevel#Warning:
```
Daffodil.setLoggingLevel(LogLevel.Warning);
```

package sapi

Overview

Failures & Diagnostics

Saving & Reloading Parsers

Type Members

class Compiler extends AnyRef

class DataLocation extends AnyRef

class DataProcessor extends WithDiagnostics

class Diagnostic extends AnyRef

class InvalidParserException extends Exception

class InvalidUsageException extends Exception

class LocationInSchemaFile extends AnyRef

class ParseResult extends WithDiagnostics

class ProcessorFactory extends WithDiagnostics

abstract class WithDiagnostics extends AnyRef

Value Members

object Daffodil

object ValidationMode extends Enumeration

package debugger

Overview

package logger

Overview

Inherited from AnyRef

Inherited from Any

Ungrouped