Thanks Bernd, Thanks for your advice, I will take a look at STX. However, do you have a prefer approach on how to start my implementation using SFire? Should I start with implementing the service class or with the WSDL?
Thanks, --danny -----Original Message----- From: Bernd Schuller [mailto:[EMAIL PROTECTED] Sent: Monday, April 17, 2006 10:27 AM To: [email protected] Subject: Re: [xfire-user] Message Translator...... Hi Danny, short answer: don't use XSLT :) XSLT is inherently DOM based, so you'll never get it to work in streaming mode. There is an alternative however, which is called STX (stx.sf.net) A Java implementation is Joost (joost.sf.net). It gives you a subset of XSLT, which is usually enough. The STX stylesheets are similar to their XSLT counterparts. I used these in a project to transform huge XML files (on the order of gigabytes), and can warmly recommend them. Best regards, Bernd. Danny Trieu wrote: > > I to implement a Message Translator as a service, i.e. WebService, to > integrate the two applications together. The two apps use difference > xml documents, therefore needed to be transformed before processing. > > I wanted to use XFire to take advantage if its fast Stax driven model > to process the transformation. My approach was to use the > MessageBinding approach with the service method accepting > /XMLStreamReader/ as the parameter representing the wrapped document > that needed to be translate before forward to its destination. My > problem is, how do use /XSLT/ with the source being StAx? To take > advantage of XFire's StAx ? If I were to use Document as the service > parameter in order to use /XSLT/ for transformation would defeat the > purpose of using StAx model right? Can someone point to implementation > approach that is Best Practice to this very commons practices? > -- Dr. Bernd Schuller Central Institute for Applied Mathematics Forschungszentrum Juelich GmbH mail [EMAIL PROTECTED] phone +49 2461 61 8736 fax +49 2461 61 6656
