[
https://issues.apache.org/jira/browse/XALANJ-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652451#action_12652451
]
Henry Zongaro commented on XALANJ-2469:
---------------------------------------
If you're using XSLT4J, your problem report should probably be directed to IBM.
However, the same problem might exist in Xalan-J, so I'll still follow up
here. I'm a bit confused by your comments: you're evaluating
/Invoice/InvoiceHeader/InvoiceParty and you say that it does return the
specified elements. Was that a typo? Did you mean to say that it "does not
return the specified element," or did you really mean that it "does return the
specified elements," but you expected it to return an empty node set?
An empty node set should be the result in this case, as a NameTest in an XPath
expression that has no prefix can only match a node that is in no namespace.
It cannot match nodes that are in the default namespace.
(There is some additional potential for confusion here, as the Xalan-J XPath
API supports a namespace prefix resolver that will permit a NameTest that has
no prefix to match nodes that were in the default namespace as supported by
that prefix resolver - but that's not the usual mode of operation.)
> 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]
