DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14185>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14185 XPathAPI.selectNodeList() fails for 'contains()' attribute expression [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-02-20 20:46 ------- I think the behavior is correct for both examples. In the XPath expression: //*[contains(@*,'Xavier')] @* returns a nodeset, which includes both attributes. A nodeset is converted to a string by returning the string-value of the first node in document order. In the XPath expression: //*[contains(record, 'Red')] //* returns all nodes in the document. When it gets to the records node, then the contains function looks for "Red" in the first child record node. When the record nodes are returned by //*, then there is no node 'record' under the context node (which is now record.) Hope that makes sense. The expression: //record[contains(.,'Red')] should return what you want. It looks for the string "Red" in all record nodes in the document.
