Using Xalan V1.4.

I have an XML which I need to transform, and in it there is an embedded XSL as 
a text node (which means
that all special XML characters are escaped). The strange thing is that even 
though the XSLT works fine, the
embedded XSL is output (non-escaped) in the transformation result even though 
its not even in the template match XPath.

I've worked around it by only letting XalanTransform work on a subtree (where 
there is no embedded XSLs), but I'm
curious to know if this behavior is by design or just a bug?

Regards,
/Rob

Reply via email to