Hi Angelo, Hhm, does your proxy web service not do anything with the request other than forwarding it to the external web service? What would be the need for the proxy then?
Anyway, you have multiple options: client -> cxf-bc consumer -> cxf-bc-provider -> external web service (no processing would occur in your cxf-bc components, message only gets passed through) client -> cxf-bc consumer -> servicemix-bean-su -> cxf-bc-provider -> external web service (any message processing can take place in servicemix-bean-su component, but it would need to deal with the message in XML format) client -> cxf-bc consumer -> servicemix-camel -> cxf-bc-provider -> external web service (instead of a servicemix-bean you could also use Camel components for etc. routing, logging, processing) client -> cxf-bc consumer -> cxf-se using cxf-proxy -> cxf-bc-provider -> external web service (your cxf-se deals with the pure payload data in Java not with XML, but since you want to pass on the same request to the external web service, the use of a cxf-proxy seems an overkill. A cxf-proxy would be more useful when making an invocation to an external web service that exposes a different WSDL) And finally you could use a http-bc component on both ends instead of a cxf-bc, whoever when it comes to processing SOAP requests, cxf-bc is recommended. Hope this helps a bit. Torsten Mielke
