Re: [dom4j-user] Re: Trying again: Node.matches() not working

[Thierry Hanser]

>And if this is the case there should be an API added to perform this
>functionality I think.
>
>thanks - dave


I guess it is the case. I am not involved in the Dom4J project
though i think it is a very good project, a good answer to
the XML/JAVA problem (DOM is too abstract and JDom does not
take enough advantage of inheritance (its hierachy is quite flat))
So i think Dom4J is a good compromise.

According to my recent tests the matches() method behaves
like one would expect from its name. The node istself must be in the
nodeset (List) resulting from the XPath évaluation.

Thus

node.matches(xpath);

returns 'true' if (and only if) 'node' belongs to the nodeset
resulting from the 'xpath' evaluation using 'node' as reference node.

Actually Dom4J delegates XPath evaluation to the Jaxen technology
that itself implements the SaxPath interface.


So there is a free space (e.g. in class Node) for a test() method with a prototype like :


boolean test(String xpath)

---

could a Dom4j team member confirm this assertion ?

Thierry




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user