list4xt : Mailing list for the XT users community.
[list4xt] Re: TraX and SAX.
Subject: [list4xt] Re: TraX and SAX.
User: Website From: Sebastien Sahuc (ssahuc@imediation.com)
Date: 03/10/2000 - 11:15
Paul T wrote :
>Hi.
>I have spend some time browsing TraX API ( http://trax.openxml.org/ )
>I mean that with Ux / SAX I can wrap most of TraX API around XT - not
changing XT code.(
>The same is not true if trying to wrap something like Ux around
TraX-conformant processor. >)
>
>Conclusion 1. TraX is not the way to go. XT ( SAX ) is. ( Not talking about
DOM - DOM part >of TraX is 'better', but who needs DOM? I don't need DOM. )
Sorry don't understand your statement, what is better than what. Unless I
missunderstood, you cannot compare Trax with SAX since one acts at the XML
level while the other acts at the transformation level. In fact there are
complementary API : Trax is using SAX2 interfaces (ContentHandler,
InputSource, etc...). So I kind of disagree with you, and I would say that
trax is the way to go...
>
>Conclusion 2. When / if somebody will need TraX around XT - this is one
week task ( almost >no need in changing XT code ).
Fine, so let's do it :-)
No, seriously, the cocoon2 project is on it way to becomme TRax based,
therefore there might be a chance to have the XT processor replacing the
Xalan when necessary.
So far I submitted a XTTransformer (Transformer in cocoon2 is a SAX2
filter), and it did a marvellous job because some bugs in Xalan1 had been
introduced. And speaking in term of performance, it's simply outstanding
compared to Xalan1. However Xalan2 should fill the gap, but it's in alpha
stage, so I thought we should get a TRax wrappers for XT, so that we -at
cocoon2- would compare performance and conformance by simply swithing
between XT and Xalan2.
Does it make sense ?
Thanks for any reply
All the best,
Sebastien
>
>Rgds.Paul.
>
>PS. Conclusion 3.
>Just make trax.Processor extends org.xml.sax.Parser, like XT does ...
--
Mailing list for the XT users community. (http://innovativepaymentprocessing.com)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)
Archive générée par hypermail 2b28 le 06/11/2001 - 11:46 CET
webmaster@4xt.org
|