L.S., First of all, welcome to ServiceMix! ;)
If you want to receive the non-soap XML message using a HTTP POST, an HTTP consumer endpoint would be the ideal solution there. For invoking the external endpoint, you could use an HTTP provider endpoint but we would generally recommend using the servicemix-cxfbc, because it is specifically geared towards dealing with web services. Once you have these two set up, you could actually choose any component that best suits your needs : servicemix-bean if you want to use a POJO, servicemix-saxon if you are going for XSL, ... My personal favorite/recommendation would be to use Camel inbetween the two endpoints: it has excellent EIP and POJO support and there are components available for XSL, EL, ... to help you build the transformations. So in a nutshell, I think the best solution for you would be: HTTP consumer -> Camel route -> CXF provider Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/5/27 Fly13DW <[email protected]>: > > Hello, > > I'm new with Apache ServiceMix, and I'm asking questions concerning the> > architecture I should use. > 1) I have a XML message as entry (no-SOAP) > <message>msg</message> > 2) This message has to be converted to be passed to an external Web Service, > using SOAP. > 3) The Web Service returns a SOAP message that has to be converted back to > XML > > I thought I use the servicemix-http for the Binding Component (1), and maybe > the servicemix-jsr181 (2). > My questions are : > - do you think there is a better Binding Component (1) to do this job? > - my servicemix-jsr181 will use a java pojo. Do I have to do a call to the > Web Service in this implemented class, or should I use another architecture? > > thank you for your answers > -- > View this message in context: > http://www.nabble.com/components-to-use-for-an-XML-to-SOAP-request-tp23745527p23745527.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
