Hi Michael,
It's really difficult to describe precisely the situations in which
this message can be produced - basically, whenever you have an XPath
expression (or a match pattern) that is syntactically incorrect, and the
point at which the XPath parser realizes that there is a syntax error is
in a place where it expected either an NCName:* or a QName to appear.
For other syntax errors, it might reach a different point in
analyzing the expression before discovering a problem, and produce a
different error. That's not particularly helpful, I know. For instance,
I can produce the message with the following template:
<xsl:template match="a[3+/child::+4]">
</xsl:template>
The error messages should provide line and column numbers. That
should at least point you to the expressions that are in error.
Perhaps Xalan-J Interpretive should also always indicate which token
it was processing when it detected the error, as a further diagnostic aid.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab Tie Line 969-6044; Phone (905) 413-6044
mailto:[EMAIL PROTECTED]
"Michael Young" <[EMAIL PROTECTED]>
04/15/2003 02:39 AM
To: <[EMAIL PROTECTED]>
cc:
Subject: Q: javax.xml.transform.TransformerException: A node
test that matches
either NCName:* or QName was expected.
Hello,
What are the other situations that can cause the following exception?
javax.xml.transform.TransformerException: A node test that matches either
NCName:* or QName was expected.
I'm migrating our xslt app to the new xalan 2.5.0, and I'm getting the
above exception. Since we have a lot of xsl files, I wonder if you guys
can give me some pointers as to the possible causes of this so that I can
fix them.
Thanks! /M.
Hi,
Some tighter error checking did go into Xalan between versions 2.3 and
2.4.
A match pattern of "." is actually invalid, so it is appropriate that
you're seeing an error message.
Ilene.
\
[EMAIL PROTECTED] \
trainer.com To: \
[EMAIL PROTECTED] \
cc: \
10/30/2002 10:19 AM Subject: Start getting
exception \
then moved to new version of Xalan
\
\
\
Hi,
I just moved from Xalan 2.3 to 2.4 and start getting this exception:
javax.xml.transform.TransformerException: A node test that matches either
NCName:* or QName was expected.
on this string in XSL:
<xsl:template match="." name="head">
That is strange because I didn't have the problem with previous version.
What it could be?
Thanks,
Jenya
