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=6329>. 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=6329 XPath does not catch CDATA Nodes ------- Additional Comments From [EMAIL PROTECTED] 2002-02-08 20:46 ------- Reminder: In the XPath data model, CDATASections are not nodes per se. They're just like any other text content. Also, the XPath data model considers all adjacent text to be a single node -- even if "adjacent" means spanning entity-reference boundaries. So when you run an XPath against a DOM and return text as a DOM node, we return the _first_ such node in the contiguous text, whether it's Text or CDATASection. It is the caller's responsibility to check whether additional text follows, if that's relevant for your application. (Note that the proposed DOM Level 3 APIs for XPath take the same approach -- except that they happen to also provide a "whole text" convenience function to make finding the other nodes and retrieving their combined content a bit easier.) I believe this explains the results you're seeing. If so, this is not a bug; it's a deliberate behavior of our API, and comes directly out of XPath's definition.
