Dave, I'm using the 2 parameter version of parseXMLStream, though I'm not providing the 2nd parameter, just using the default value. Regardless, in the Xalan code I have (v1.10), ensureDOMParser is not called, but rather createDOMParser is.
Michael Albers -----Original Message----- From: David Bertoni [mailto:dbert...@apache.org] Sent: Tuesday, September 15, 2009 12:37 PM To: xalan-c-users@xml.apache.org Subject: Re: Modifying behavior of XercesParserLiaison Albers, Michael wrote: > Hello, > > I've been trying to use the > XercesParserLiaison::setExternalSchemaLocation function call and have > found that it has no effect. Looking at the source code for > XercesParserLiaison it appears that none of the behavior modification > get/set functions actually have any effect because the > XercesParserLiaison::ensureDOMParser call is never made and can't be > called by the user. Will this be changed in a future release of Xalan? > In the meantime, is there any way to work around this? It isn't > critical for me at this point but the XercesParserLiaison API is very > misleading. XercesParserLiaison::ensureDOMParser() is called by XercesParserLiaison::parseXMLStream(const InputSource& inputSource, const XalanDOMString& identifier), from what I can tell. Are you perhaps calling the version the overload that accepts a DocumentHandler? Since the SAXParser doesn't support schema processing, there's no reason to use those properties for that call. I will tighten up the documentation for the property calls to clarify the situation. Dave
