|
| | |
SAX2Print uses the SAX2 APIs to parse an XML file and print
it back. Do note that the output of this sample is not
exactly the same as the input (in terms of whitespaces, first
line), but the output has the same information content as the
input.
| | |
The SAX2Print sample parses an XML file and prints out the
contents again in XML (some loss occurs). To run SAX2Print,
enter the following
The following parameters may be set from the command line
 | | | |
Usage:
SAX2Print [options] <XML file>
This program invokes the SAX2XMLReader, and then prints the
data returned by the various SAX2 handlers for the specified
XML file.
Options:
-u=xxx Handle unrepresentable chars [fail | rep | ref*].
-v=xxx Validation scheme [always | never | auto*].
-e Expand Namespace Alias with URI's.
-x=XXX Use a particular encoding for output (LATIN1*).
-f Enable full schema constraint checking processing. Defaults to off.
-p Enable namespace-prefixes feature. Defaults to off.\n"
-n Disable namespace processing. Defaults to on.\n"
NOTE: THIS IS OPPOSITE FROM OTHER SAMPLES.\n"
-s Disable schema processing. Defaults to on.
NOTE: THIS IS OPPOSITE FROM OTHER SAMPLES.
-? Show this help.
* = Default if not provided explicitly.
The parser has intrinsic support for the following encodings:
UTF-8, US-ASCII, ISO8859-1, UTF-16[BL]E, UCS-4[BL]E,
WINDOWS-1252, IBM1140, IBM037, IBM1047.
| | | | |
-u=fail will fail when unrepresentable characters are encountered
-u=rep will replace with the substitution character for that codepage
-u=ref will report the character as a reference
-v=always will force validation
-v=never will not use any validation
-v=auto will validate if a DOCTYPE declaration or a schema declaration is present in the XML document
Here is a sample output from SAX2Print
| | | | cd xerces-c-3.3.0/samples/data
SAX2Print -v=always personal.xml
<?xml version="1.0" encoding="LATIN1"?>
<personnel>
<person id="Big.Boss">
<name><family>Boss</family> <given>Big</given></name>
<email>chief@foo.com</email>
<link subordinates="one.worker two.worker three.worker
four.worker five.worker"></link>
</person>
<person id="one.worker">
<name><family>Worker</family> <given>One</given></name>
<email>one@foo.com</email>
<link manager="Big.Boss"></link>
</person>
<person id="two.worker">
<name><family>Worker</family> <given>Two</given></name>
<email>two@foo.com</email>
<link manager="Big.Boss"></link>
</person>
<person id="three.worker">
<name><family>Worker</family> <given>Three</given></name>
<email>three@foo.com</email>
<link manager="Big.Boss"></link>
</person>
<person id="four.worker">
<name><family>Worker</family> <given>Four</given></name>
<email>four@foo.com</email>
<link manager="Big.Boss"></link>
</person>
<person id="five.worker">
<name><family>Worker</family> <given>Five</given></name>
<email>five@foo.com</email>
<link manager="Big.Boss"></link>
</person>
</personnel> | | | | |
 | SAX2Print does not reproduce the original XML file.
SAX2Print and DOMPrint produce different results because of
the way the two APIs store data and capture events. |
|
|
|
|
