Hi, All --
There is an issue with the way that Node#getStringValue() current functions. As per the Javadocs:
http://dom4j.org/apidocs/org/dom4j/Node.html#getStringValue()
This is supposed to return the String value of a Node in the XPath sense, and Jaxen relies on this in the dom4j Navigator implementation. *However*, XPath doesn't believe in two adjacent text nodes, so if I have a tree that looks like:
<x> |-#text:Some TEXT |-#cdata:some CDATA |-#text:Some more TEXT
XPath things that the #text, #cdata, and #text are all the *same* text node, so if I ask for cdataNode.getStringValue(), it shoudl return "Some TEXTsome CDATASome more TEXT".
I haven't reported this as a bug, because it isn't clear what should be done about it:
1) Change the API description to vary from XPath and then change the Jaxen Navigator.
2) Change the implementaiton to comply with the XPath spec.
Thoughts?
-- Paul
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ dom4j-dev mailing list dom4j-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-dev
