axproject.org">http://www.saxproject.org.
For a complete description of how SAXBuilder is used, and how to customise the process you should look at the {@link org.jdom2.input.sax} packagedocumentation.
JDOM users needing to customise the SAX parsing process have traditionally sub-classed this SAXBuilder class. In JDOM2 this should never be necessary. Please read the full documentation of this class, {@link SAXHandler}, {@link SAXHandlerFactory}, {@link JDOMFactory}, and the package documentation for {@link org.jdom2.input.sax} before overriding this class. Future versionsof JDOM2 may make this class 'final'. I you feel you have a good reason to subclass SAXBuilder please mention it on jdom-interest mailing list so that SAXBuilder can be extended or adapted to handle your use-case.
Neither SAXBuilder nor anything derived from SAXBuilder is thread-safe. You must ensure that SAXBuilder is used in a single thread, or that sufficient locking is in place to ensure that SAXBuilder is not concurrently accessed. See the special note on {@link #buildEngine()}.
Known issues:
- Relative paths for a {@link DocType} or {@link EntityRef} may beconverted by the SAX parser into absolute paths.
- SAX does not recognise whitespace character content outside the root element (nor does JDOM) so any formatting outside the root Element will be lost.
@see org.jdom2.input.sax
@author Jason Hunter
@author Brett McLaughlin
@author Dan Schaffer
@author Philip Nelson
@author Alex Rosen
@author Rolf Lear