Page 1 of 1

XWatch evaluation error

Posted: Tue Oct 12, 2004 8:50 pm
by kilhor
Dear, I battle the following problem with XWatch when debugging XSLT.

Having this XSL

Code: Select all


<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0">
<xsl:output />
<xsl:template match="//xs:element">
Found.
</xsl:template>
</xsl:stylesheet>
and this XML (here by accident XML Schema)

Code: Select all


<?xml version="1.0" encoding="UTF-8"?>
<!-- Copyright P&P Software GmbH (Zurich, Switzerland) -->
<xs:schema targetNamespace="xxx" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/XMLSchema schema.schema">
<xs:element name="Comment" type="xs:string"/>
</xs:schema>
When using the XWatch while debuging and asking for /* I get the NodeSet that contains xs:schema -- that's fine. BUT if I ask for /xs:schema I get an error. What is wrong?

Thanks & Regards

Kilhor


PS: The problem is not limited to the example above, this is just a test case.[/b]

Problem solved

Posted: Wed Oct 13, 2004 12:40 pm
by Radu
Dear Kilhor,

Thank you for reporting this problem.
The problem was solved for all the debugging processors and the fix will be available in the next release.



Regards,
Radu.

Posted: Wed Oct 13, 2004 12:59 pm
by kilhor
Thanks for answer. In the meantime, does it help to migrate from Saxon to some other XSLT processor that doesn't have this problem?

Posted: Wed Oct 13, 2004 10:43 pm
by george
Hi Kilhor,

No, the debugger implementation based on Xalan has the same behavior.

Best Regards,
George