[
Lists Home |
Date Index |
Thread Index
]
<snip/>
> I still don't understand why validation is not performed in a SAX filter
> rather than in parsers. Parsers like Xerces have dramatically grown in
size
> and have performance problem due to the fact that validation is built in
in
> the parser.
>
> To me, parsing and validating are two different activities. They may have
> been integrated for performance reasons of the parsing+validation
pipeline,
> but I'd still like to have a clean, high performance parsing pipeline in
> which I could plugin any kind of validators (eg. Sun MSV).
<snip/>
In GNU JAXP they are-- within the Pipeline package there is a
ValidationConsumer. Currently this only supports DTD validation, but it is
cleanly layered so that it operates on a SAX stream of events and does not
deal with parsing. Because of this separation, though, there are many tests
/ VCs that cannot be reported because parsers may normalize input before
passing it through. For example, multiple DTD declarations might not be
reported-- additionally there are lexical errors that won't necessarily be
caught.
See the help for ValidationConsumer for more information:
http://www.gnu.org/software/classpathx/jaxp/apidoc/gnu/xml/pipeline/Validati
onConsumer.html
Cheers!
Jeff Rafter
Defined Systems
http://www.defined.net
XML Development and Developer Web Hosting
|
