On 2/21/2011 3:39 PM, Kellogg, Phillip A wrote:
Hello,
I am trying to set an external schema location for xalan/xerces to use
so that I can specify a specific path to where my schema is located, a
relative path specified in the XML instance is not acceptable. Looking
at the Xalan API, my XalanSourceTreeParserLiaison object should be able
to do this via setExternalSchemaLocation(). However, once the schema
location makes it to the XercesParserLiaison, the string is never used.
As stated in another thread, dated Tue, 15 Sep 2009 15:10:44 GMT, there
is a function, XercesParserLiaison::ensureDOMParser() that should take
care of this. In a subsequent unreleased version of this class, that
function is now called when parseXMLStream() is called.
&nb sp;
It appears that Xalan 1.10, the version I am using, was released in
2005. I don’t have the ability to use an unreleased version of Xalan and
am wondering if there will be another release of Xalan in the near
future? Or is there some other workaround that I could employ to get
this to work.
I doubt there will ever be another release of Xalan-C. I don't have the
time to resurrect the release process, and the people who were familiar
with it are long gone.
If you need that fix, you can either update to the head of the
subversion repository, or you can attempt to patch the changes I made to
fix the problem. The Jira issue is XALAN-667 and the SVN revision number
is 637487.
Either way, you will end up with an unofficial version of Xalan-C, so it
will be much simpler if you just use the head of the repository.
Dave
