  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Dom api Vs Jdom api to evaluate xpath in Jaxen | Dom api Vs Jdom api to evaluate xpath in Jaxen 2007-03-14 - By Deepa Janamatti (RBIN/EMT2)
Back Hello, 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.
Regards, Deepa
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59"> <TITLE>Dom api Vs Jdom api to evaluate xpath in Jaxen</TITLE> </HEAD> <BODY> <!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">Hello,</FONT>
<BR><FONT SIZE=2 FACE="Arial">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? </FONT></P>
<P><FONT SIZE=2 FACE="Arial">Thanks in advance.</FONT> </P>
<P><FONT SIZE=2 FACE="Arial">Regards,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Deepa</FONT> </P>
</BODY> </HTML> __ ____ ____ ____ ____ ____ ____ ____ ____ ____ To control your jdom-interest membership: http://www.jdom.org/mailman/options/jdom-interest/youraddr@(protected)
|
|
 |