Subjects
Home
Xalan extension functions
Fomatting question serializing DOM with pretty print
xalan with pull parser
Cannot find the declaration
Apache Xalan drop support to run on JRE 1 1 x
Why does Doctype change processing of a document
Node set to XML string via Java extensions in Xalan J: possible?
Templates/Transformers + thread safety???
Problem evaluating xpath with muliple prefix with different namespace
remove an arbitrary attribute from xsl output
Xalan3 XSLT 2 0 XPath 2 0 support?
Problem using compiled translets with Xalan !!
Xalan and jstl 1 1 problem with transform tag
NullPointer in DOM2DTM getLocalName
URIResolvers base parameter with xsltc and cascaded imports
Performance problem for Xalan J on intel dual core
Standard libraries in JAXP?
Serializing a DOM tree to XML file, customize entities replacement
Library Conflict Involving BCEL Library
A question on how users are using <xsl:message >
Kevin Cormier as a new Apache Xalan J committer
Struggling to iterate over tokenized string
Xalan count() trouble
Problem with recursive xpath
Error when switching to java 1 5
document( ' ')
Problem with Xalan2 7 0 transformation
cr/lf options
entity encoded XML
can xalan transform 2 xml using one xslt?
Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
xsl transform with cdata section elements
xslt parameters not expanded
Weird behavior of XPath evaluate()
How to avoid <xsl:message > instruction prints stylesheet file informations ?
Cannot find SimpleTransform subdirectory after installing Xalan J
recover from document not found exceptions
jdk1 5 and Xalan jar differences?
Performance Issue
Error/Bug adding floating point numbers
XPathAPI: eval exp using nodes with default namespace
modifying xalan to output invalid XML
NullPointerException
mege two separate xml nodes into one
Is this a XALAN document identification bug?
is StylesheetRoot really java io Serializable ?
transform() fails for DOMSource but succeeds for StreamSource
Thoughts on Transformer parameter passing
HELP, Xalan and jstl 1 1 problem with transformer
Problem with XPath namespace axis?
string utils:replace deleting search string if replacement string is an HTML
help with enumeration values pls
xalan 2 5 1 vs 2 7 performance question
How to insert/update in XML document
HTML Serialization and Handling of Ampersands in HREF Attributes
XHTML link tag stripping
SystemId Unknown; Line #24; Column #49; java lang NullPointerException
xpath text() help
Apostrophe problem with xalan 2 7 0
How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Re: Q: javax.xml.transform.TransformerException: A node test that matches
eith

Re: Q: javax.xml.transform.TransformerException: A node test that matches
eith

2003-04-15       - By Henry Zongaro

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:zongaro@(protected)




"Michael Young" <javaone@(protected)>
04/15/2003 02:39 AM


       To:     <xalan-j-users@(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.



           \

                     evgeniy.strokin@(protected)            \

                     trainer.com                  To:       \
               xalan-j-users@(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