Yes, when designing VTD-XML we took a long hard look at JAXP...
the conclusion is that JAXP simply has too many issues... the problem starts
from the DOM API (which I have written an article on this topic called
the performance woe of binary XML
http://webservices.sys-con.com/read/250512.htm)
The second major problem is JAXP's xpath evaluation model which I have
written another article called "improve XPath efficiency with VTD-XML"
http://www.devx.com/xml/Article/34045)... basic JAXP's evaluation model
is not only slow but cluttered and hard to use...
If one can pick up an XPath engine and write highly readable, clean ,
reusable
code that 10x faster... why would anyone settle for JAXP? In a way, XML is
meant to decouple API from data anyway...
----- Original Message -----
From: "James Strachan" <[EMAIL PROTECTED]>
To: <users@activemq.apache.org>
Sent: Tuesday, February 26, 2008 9:48 PM
Subject: Re: VTD-XML 2.3
On 26/02/2008, jimmy Zhang <[EMAIL PROTECTED]> wrote:
My take (which I am going publish articles shortly) is that VTD-XML
is vastly superior to JAXP in routing/switching XML payloads...
JAXP is just an API for XPath. I don't see why VTD-XML can't implement
that API - it'd make it really easy for XPath users to switch to using
VTD-XML?
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/xpath/package-summary.html
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
