[jdom-interest] Dom api Vs Jdom api to evaluate xpath in Jaxen

Michael Kay mike at saxonica.com
Wed Mar 14 03:34:27 PST 2007

I'm only guessing, but DOM has many features that are very unfriendly to
XPath processing, such as adjacent text nodes, CDATA and entity reference
nodes, and it's very inefficient at least in DOM level 2 to compare nodes
for identity or document order.
Michael Kay


From: jdom-interest-bounces at jdom.org [mailto:jdom-interest-bounces at jdom.org]
On Behalf Of Deepa Janamatti (RBIN/EMT2)
Sent: 14 March 2007 10:33
To: jdom-interest at jdom.org
Subject: [jdom-interest] Dom api Vs Jdom api to evaluate xpath in Jaxen

I have tried evaluating the xpath queries using the JDOM xpath api and also
using the w3c DOM xpath api of Jaxen. But querying using the JDOM api was
faster. Can you please explain me why this has happened?

Thanks in advance. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.jdom.org/pipermail/jdom-interest/attachments/20070314/071419c1/attachment.htm

More information about the jdom-interest mailing list