Hi, I think I've run into a bug in the CXFBC-Consumer. When using a WSDL with a structure like the following:
<wsdl:operation name="someOperation"> <soap:operation soapAction="http://some.name/space/someOperation"; style="document"/> <wsdl:input> <soap:header message="tns:someHeaderMessage" part="SomePart" use="literal"/> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> If I associate a wsdl with a structure like the above with the CXFBC consumer, the output JBI message contains the custom header in both the JBI message body as a JBI part and the JBI message header. When this message reaches the corresponding CXFBC Provider, the outgoing soap message contains the custom header twice. If I remove the soap:header from the wsdl:input on the CXFBC consumer, the message structure is correct through the entire chain. Has anyone else encountered this problem? Is it indeed a bug? Thanks. -- View this message in context: http://www.nabble.com/CXFBC-Consumer-bug-tp21130607p21130607.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
