Assuming this is similar to the XML4J 2.0.x code I've worked with, XMLDocumentHandler is _not_ part of the SAX support. It's an internal stage, used to drive special-purpose listeners that employ deferred resolution of strings.
If you want to understand the full chain of events that causes the SAX DocumentHandler to be called, an XMLDocumentHandler may involved somewhere in the process. But if you just want to create and plug in a SAX DocumentHandler, ignore XMLDocumentHander entirely. (XMLDocumentHandler seems to have been removed from the newest Java version. I'm not entirely sure what replaces it.) ______________________________________ Joe Kesselman / IBM Research
