James, thanks for your answer. However, I don't think the BasicMessageFilter is responsible for the breadcrumbId not being picked up. The filter is about populating the SOAP header element from exchange headers, not the other way round. My proxy does not use spring-ws, but works on plain http. The proxy does some inspection of the raw SOAP XML and SAML header and on success forwards the request. The breadcrumbId is set as an HTTP header as expected on the forward. But it is not unmarshalled as an exchange header in my web service route. The documentation page for MDC logging claims that the header survives across an HTTP transport. Though might be I am expecting too much and the claim to support HTTP transport does not include X over HTTP. But really just plain HTTP endpoints.
This is my proxy route: Ralf -- View this message in context: http://camel.465427.n5.nabble.com/breadcrumbId-does-not-survive-http-call-tp5762528p5762566.html Sent from the Camel - Users mailing list archive at Nabble.com.
