> Agghhh!
> This reply-not-going-to-the-list business gets me every time!
>
> Well, by trial and error, I discovered it's a DOMException (code 14 -
> namespace error).
OK, this is a bug, because we should not let a DOMException through -- it
should be caught by the wrapper code and translated into a
XalanDOMException.
> Why I'm getting such an error, I'm not sure. There's certainly nothing
> wrong with the namespace declarations in either the source document or
> the xslt document.
I'm going to grep through the Xerces-C code and see where that exception
might be thrown. It could be a bug in the implementation.
> The actual method being called is:
>
> int transform (const XalanParsedSource &theParsedXML,
> const XalanCompiledStylesheet *theCompiledStylesheet,
> const XSLTResultTarget > &theResultTarget)
>
> The compiled stylesheet was compiled from an XSLTInputSource specified
> as a SYSTEM-id (http://localhost/...).
> The parsed source was compiled from a XercesDOMWrapperParsedSource.
What is the target of the transformation? Perhaps a DOM? Or is it a
stream? Are you sure you cannot reproduce it with testXSLT? I think
there's still an option on testXSLT to use the Xerces DOM from the command
line. (-XD)
Dave
