Kelly Graus wrote:
Ok, that makes sense. And good news with the future inclusion of the
XMLEntityResolver.
In the mean time, I got my custom entity resolver working when I use the
path to the XML file in the transform call (before I wasn't setting the
system IDs correctly in the InputSources, which was causing the working
directory to be passed in to the entity resolver). However, when I try
to use a Xerces DOM as the XML input, it doesn't seem to use the system
id that the DOM has, or the system id that I set in the
XercesDOMWrapperParsedSource, and ends up using the working directory.
Is there another way to set the system id for the XML when using a
Xerces DOM as the source?
It's hard to say without seeing some real source code. This could be a
bug, or it could be a problem with your code.
Can you post a minimal amount of source code that reproduces the problem?
Dave
