L.S., You can also configure the CXF BC provider endpoint to handle the Soap envelope directly instead of expecting a JBI-wrapped message by adding the useJBIWrapper='false' attribute to the endpoint definition.
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/9/24 angel.ortiz <[email protected]>: > > > Hi Willem, > > Thanks for the info. So, I must transform my SOAP request: > > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:info="http://path.to.service/InformationService/";> > <soapenv:Body> > <info:displayInformation> > <approver>000000001</approver> > </info:displayInformation> > </soapenv:Body> > </soapenv:Envelope> > > into a JBI message like this: > > <jbi:message xmlns="http://java.sun.com/xml/ns/jbi"; > xmlns:jbi='http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper' > > <jbi:part> > <displayInformation > xmlns="http://path.to.service/InformationService/";> > <approver>000000001</approver> > </displayInformation> > </jbi:part> > </jbi:message> > > Is this correct? Am I missing something? > > Thanks, > Angel > -- > View this message in context: > http://www.nabble.com/Web-Services-Virtualization-using-ServiceMix-tp25514386p25571788.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
