On 27/02/2008, jimmy Zhang <[EMAIL PROTECTED]> wrote: > 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...
OK thanks for the heads up :) So we just need a volunteer to submit a patch for the VTD-XML plugin for camel-extra.. http://code.google.com/p/camel-extra/issues/detail?id=2 I'll add it to my list if noone else jumps in :) -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
