This assumes the plain XML content has already been preprocessed first and attached with the VTD indices, right?

Plus VTD-XML and Saxon/XSLT are different things, it would be interesting to see Saxon can have VTD-XML as a plugin though.

On 8/19/06, Jimmy Zhang <> wrote:
VTD-XML is far more efficient (CPU/memory wise) than SAXON in splitting XML,
there is no comparison...

VTD-XML fully supports XML path, so split pattern can get as complex as

----- Original Message -----
From: "andrew welch" <>
To: "Mailing list for SAXON XSLT queries" <>
Sent: Sunday, August 06, 2006 3:22 AM
Subject: Re: [saxon] Odd issue with Saxon.

> On 8/4/06, Jimmy Zhang < > wrote:
>> I suggest that you take a look at this article...
>> Using XSLT to split XML is an overkill....
> It is when the split is this simple, but if requirements were to
> change and the split became only slightly more complicated then XSLT
> would be the ideal tool.  The split is often a one-off operation, so
> performance is less important.
> <OT> I had a look a VTD-XML (albeit a very quick one) and I wasn't
> that impressed...  has anyone used it and can recommend it as "the"
> way to manipluate XML in java? </OT>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join 's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> _______________________________________________
> saxon-help mailing list

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
saxon-help mailing list