Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 87050 invoked from network); 26 Feb 2008 20:19:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2008 20:19:36 -0000 Received: (qmail 55844 invoked by uid 500); 26 Feb 2008 20:19:30 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55822 invoked by uid 500); 26 Feb 2008 20:19:30 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 55813 invoked by uid 99); 26 Feb 2008 20:19:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2008 12:19:30 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of crackeur@comcast.net designates 76.96.30.56 as permitted sender) Received: from [76.96.30.56] (HELO QMTA06.emeryville.ca.mail.comcast.net) (76.96.30.56) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Feb 2008 20:18:40 +0000 Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA06.emeryville.ca.mail.comcast.net with comcast id uKDx1Y0020FhH24A605000; Tue, 26 Feb 2008 20:18:33 +0000 Received: from your55e5f9e3d2 ([67.164.81.9]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id uLJy1Y00H0C3pGr8U00000; Tue, 26 Feb 2008 20:19:00 +0000 X-Authority-Analysis: v=1.0 c=1 a=mV9VRH-2AAAA:8 a=1XWaLZrsAAAA:8 a=2z1OXlWFAAAA:8 a=FP58Ms26AAAA:8 a=Fg8anum3AAAA:8 a=fziSbYi_AAAA:8 a=ycZRORMMAAAA:8 a=Rr5kw0T3AAAA:8 a=yrh8Z8tmAAAA:8 a=W2TqWKmsAAAA:8 a=ASKJA2OWCXHAAJd63aYA:9 a=DokeECu5tnY_oovlBP4A:7 a=zKnhce--wDLUCIXJgCYeAfCsK1wA:4 a=vxBcW1QQACsA:10 a=MSl-tDqOz04A:10 a=si9q_4b84H0A:10 a=Rp11AdlyIvgA:10 Message-ID: <001401c878b4$d3622490$0402a8c0@your55e5f9e3d2> From: "jimmy Zhang" To: References: <003e01c87807$a79bf820$0402a8c0@your55e5f9e3d2> Subject: Re: VTD-XML 2.3 Date: Tue, 26 Feb 2008 12:19:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Virus-Checked: Checked by ClamAV on apache.org My take (which I am going publish articles shortly) is that VTD-XML is vastly superior to JAXP in routing/switching XML payloads... it is my understanding that in the most typical cases VTD-XML will shock the world (outperforming JAXP by about 10~100x) We support full XPath expression but again, if you look under the hood, the techcal savvy subscrber of this list will agree with me that JAXP (DOM/SAX) is fundamentally broken... ----- Original Message ----- From: "James Strachan" To: Sent: Tuesday, February 26, 2008 12:13 PM Subject: Re: VTD-XML 2.3 >I guess VTD-XML is more suitable for the Camel sub project; we could > use it for XML routing and so forth. > http://activemq.apache.org/camel/ > > Given the fact that VTD-XML appears GPL we'd not be able to host it at > Apache, but we could host it at the camel-extra project... > http://code.google.com/p/camel-extra/ > > Does VTD-XML support the JAXP XPath API? Or any plans to? :) It'd > certainly make it a bit easier to integrate, but its not essential. > > > On 25/02/2008, jimmy Zhang wrote: >> VTD-XML 2.3 (http://vtd-xml.sf.net) is now released. To download the >> latest >> version please visit >> >> http://sourceforge.net/project/showfiles.php?group_id=110612&package_id=1201 >> 72. >> >> Below is a list of new features and enhancements in this version. >> >> * VTDException is now introduced as the root class for all other >> VTD-XML's >> exception classes (per suggestion of Max Rahder). >> * Transcoding capability is now added for inter-document cut and paste. >> You >> can cut a chuck of bytes in a UTF-8 encoded document and paste it into a >> UTF-16 encoded document and the output document is still well-formed. >> * ISO-8859-10, ISO-8859-11, ISO-8859-12, ISO-8859-13, ISO-8859-14 and >> ISO-8859-15 support has now been added >> * Zero length Text node is now possible. >> * Ability to dump in-memory copy of text is added. >> * Various code cleanup, enhancement and bug fixes. >> >> >> Below are some new articles related to VTD-XML >> >> *Index XML documents with VTD-XML http://xml.sys-con.com/read/453082.htm >> >> *Manipulate XML content the Ximple Way >> http://www.devx.com/xml/Article/36379 >> >> * VTD-XML: A new vision of XML >> http://www.developer.com/xml/article.php/3714051 >> >> * VTD-XML: XML Processing for the future >> http://www.codeproject.com/KB/cs/vtd-xml_examples.aspx >> >> If you (or someone you know) like the concept of VTD-XML, think that it >> can >> help solve enterprises' XML processing related issues (particularly >> those >> related to SOA), and would like to directly influence and contribute to >> the >> development of the future of Internet, please email me >> (crackeur@comcast.net). We are looking for open source software >> developers >> and project management people to take VTD-XML to the next level. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org >> For additional commands, e-mail: user-help@xmlbeans.apache.org >> >> >> > > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com >