Guillaume, 1) If we switch to using the servicemix-http does it support the shouldIncludeHeader() type operation that the SaajMarshaler supports, because we found we needed to exclude certain HTTP Headers (e.g the Content-Type as it was appearing twice in the message sent to the destination web service).
2) Can you review our usage of ServiceMix, maybe we're using ServiceMix incorrectly :- a) We send a normalized xml message (not a soap message) into the ESB via Http. b) Message is received by HttpConnector - forwards to eip content-based-router c) This message gets routed using the eip content-based-router, the destination may or may not be a web service - depending on the consumer destination. d) Where it is for a web service we forward to the SAAJBinding component (however we extended the servicemix SAAJBinding to add a soap action and inject it via xml) Our requirements are : - to send messages to ESB via HTTP (or in future JMS), - Add SOAP Actions if necessary, - remove superfluous HTTP Headers (these caused an issue for the receipient web service) cheers Pete -- View this message in context: http://www.nabble.com/SAAJMarshaller---soapfault-content-getting-removed-t1830872.html#a5009219 Sent from the ServiceMix - User forum at Nabble.com.
