XSLTProcessorEnvSupportDefault::parseXML() uses the current
XMLParserLiaison instance, so as long as the EntityResolver instance is
installed into the instance, everything should work as planned. Perhaps
there's a bug?
Dave
|---------+--------------------------->
| | "Brian Quinlan" |
| | <brian@sweetapp.|
| | com> |
| | |
| | 04/25/2002 08:45|
| | AM |
| | Please respond |
| | to xalan-dev |
| | |
|---------+--------------------------->
>---------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: Should EntityResolver be used in XSLTProcessorEnvSupportDefault
|
>---------------------------------------------------------------------------------------------------------------------------|
EntityResolver can be used to resolve external XML entities. It can also
be used to resolve import/include instructions. But, AFAIK, there is no
way to use it to resolve entities specified in the document() XPath
function without subclassing XSLTProcessorEnvSupportDefault and
reimplementing parseXML.
Is my analysis correct? If so, should there be a way of installing an
EntityResolver in XSLTProcessorEnvSupportDefault?
Cheers,
Brian
