[
https://issues.apache.org/jira/browse/XALANJ-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652797#action_12652797
]
Henry Zongaro commented on XALANJ-2469:
---------------------------------------
In my preceding analysis, I neglected to include a crucial reference to section
5.1 of XPath.[4] That section states, "An element node has an expanded-name
computed by expanding the QName of the element specified in the tag in
accordance with the XML Namespaces Recommendation [XML Names]." It's the XML
Namespaces recommendation that defines the concept of "expanded name", and
there you'll find that the expanded name of a element node that has no prefix
still has a namespace URI if there is a default namespace. That's in contrast
to section 2.3 of XPath, where the expanded name for a node test that is a
QName that has no prefix has a null namespace URI. That's the reason the node
test does not match in this situation, despite the fact two QNames are
syntactically identical.
[4] http://www.w3.org/TR/xpath#element-nodes
> Xpath support in Xalan does not work if default namespace is used
> -----------------------------------------------------------------
>
> Key: XALANJ-2469
> URL: https://issues.apache.org/jira/browse/XALANJ-2469
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: XPath
> Affects Versions: 2.0.x
> Environment: Windows, IBM WebSphere Application Server - ND,
> 6.1.0.7
> Reporter: rohit singh
> Priority: Blocker
> Fix For: 2.0.x
>
>
> We are trying to use path for example "/Invoice/InvoiceHeader/InvoiceParty"
> as an X-Path expression. The XML document on which this xpath is evaluated
> has a default namespace defined. This xpath expression does return the
> specified elements value. I check the specification on xpath 1.0 on this url
> http://www.w3.org/TR/xpath and got this text below
> "There is an element node for every element in the document. An element node
> has an expanded-name computed by expanding the QName of the element specified
> in the tag in accordance with the XML Namespaces Recommendation [XML Names].
> The namespace URI of the element's expanded-name will be null if the QName
> has no prefix and there is no applicable default namespace."
> According to the above the xpath should work irrespective of whether we have
> specified a default namespace or not. Please take this as a high priority and
> fix this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
