Well, Jaxen, the xpath engine that dom4j uses, is an abstraction
above bare-metal dom APIs, so will be slightly slower. Jaxen is
continuously improving to reduce the amount of overhead added.
Though, for developers hours spent, xpath will save you tons.
Much easier to write:
/foo/bar/baz[cheese='gouda']
than the equivalent using bare-metal APIs. Plus, time to debug,
etc.
I'd say give xpath a chance, and if it underperforms, tell the
jaxen team, and only after exhausting those possibilities, go
to the bare-metal.
-bob
On Fri, 17 Oct 2003, pramod wrote:
> Hello ,
> I am developing an application, which compares data from xml files
> with size around 1mb each .
> currently i am using th traditional DOM api i.e org.w3c.xml.in Java
> I want to know whether using Xpath will help me in increase the speed , as
> we can directly specify the paths of the nodes while searching . should i go
> for XPath or use the same Dom apis to traverse various nodes in the
> document.
>
> Thanks
>
> Pramod
>
>
>
--
Bob McWhirter [EMAIL PROTECTED]
The Werken Company http://werken.com/
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user
