|
Hi all, 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? Also, How would I start my implementation of the service: 1) start with
writing the WSDL that describe my service interface, including the <wsdl:types/>
that has the schema of my xml inDoc that need to be translate? Or 2) I define the
service interface like this: Interface MyService { XMLStreamReader/Document
invoke( XMLStreamReader/Document theDocument ) ; } And generated the WSDL. And may be modify the generated WSDL’s <wsdl:types/> to
include the schema of the inDoc? Thanks for any help, --danny |
- [xfire-user] Message Translator...... Danny Trieu
- Re: [xfire-user] Message Translator...... Bernd Schuller
- Re: [xfire-user] Message Translator...... Bernd Schuller
- RE: [xfire-user] Message Translator...... Danny Trieu
- Re: [xfire-user] Message Translator...... Dan Diephouse
- RE: [xfire-user] Message Translator...... Danny Trieu
- RE: [xfire-user] Message Translator...... Danny Trieu
- Re: [xfire-user] Message Translator...... Bernd Schuller
