Parses the input stream into a yaidom Document
.
Parses the input stream into a yaidom Document
. Closes the input stream afterwards.
Parses the content of the given File into a eu.cdevreeze.yaidom.Document.
Parses the content of the given File into a eu.cdevreeze.yaidom.Document.
Parses the content of the given URI into a eu.cdevreeze.yaidom.Document.
Parses the content of the given URI into a eu.cdevreeze.yaidom.Document.
DOM-LS-based
Document
parser.Typical non-trivial creation is as follows, assuming class
MyEntityResolver
, which extendsLSResourceResolver
, and classMyErrorHandler
, which extendsDOMErrorHandler
:A custom
LSResourceResolver
could be used to retrieve DTDs locally, or even to suppress DTD resolution. The latter can be coded as follows (see http://stuartsierra.com/2008/05/08/stop-your-java-sax-parser-from-downloading-dtds), risking some loss of information:For completeness, a custom
DOMErrorHandler
class that simply throws an exception:If more flexibility is needed in configuring the
DocumentParser
than offered by this class, consider writing a wrapperDocumentParser
which wraps aDocumentParserUsingDomLS
, but adapts theparse
method. This would make it possible to set an encoding on theLSInput
, for example. As another example, this would allow for adapting the conversion from a DOMDocument
to yaidomDocument
.A
DocumentParserUsingDomLS
instance can be re-used multiple times, from the same thread. If theDOMImplementationLS
is thread-safe, it can even be re-used from multiple threads. Typically aDOMImplementationLS
cannot be trusted to be thread-safe, however. In a web application, one (safe) way to deal with that is to use oneDOMImplementationLS
instance per request.