Prev Class | Next Class | Frames | No Frames |
Summary: Nested | Field | Method | Constr | Detail: Nested | Field | Method | Constr |
java.lang.Object
gnu.xml.util.DoParse
The SAX2 XMLReaderFactory should return a SAX2 XML parser which supports both of the standardized extension handlers (for declaration and lexical events). That parser will be used to produce events.
The first parameter to the command gives the name of the document that will be given to that processor. If it is a file name, it is converted to a URL first.
The second parameter describes a simple processing pipeline, and will
be used as input to PipelineFactory
methods which identify the processing to be done. Examples of such a
pipeline include
nsfix | validate to validate the input document nsfix | write ( stdout ) to echo the file as XML text dom | nsfix | write ( stdout ) parse into DOM, print the result
Relatively complex pipelines can be described on the command line, but not all interesting ones will require as little configuration as can be done in that way. Put filters like "nsfix", perhaps followed by "validate", at the front of the pipeline so they can be optimized out if a parser supports those modes natively.
If the parsing is aborted for any reason, the JVM will exit with a failure code. If a validating parse was done then both validation and well formedness errors will cause a failure. A non-validating parse will report failure on well formedness errors.
PipelineFactory
Method Summary | |
static void |
|
Methods inherited from class java.lang.Object | |
clone , equals , extends Object> getClass , finalize , hashCode , notify , notifyAll , toString , wait , wait , wait |
public static void main(argv[] ) throws IOException
Command line invoker for this class; pass a filename or URL as the first argument, and a pipeline description as the second. Make sure to use filters to condition the input to stages that require it; an nsfix filter will be a common requirement, to restore syntax that SAX2 parsers delete by default. Some conditioning filters may be eliminated by setting parser options. (For example, "nsfix" can set the "namespace-prefixes" feature to a non-default value of "true". In the same way, "validate" can set the "validation" feature to "true".)