camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Carman <>
Subject Re: breadcrumbId does not survive http call
Date Tue, 10 Feb 2015 14:06:13 GMT
It's an easy thing to test, right?  Just copy/paste the default impl
into your source and modify it NOT to remove the header.  If you're
right, the problem will still be there.  If I'm right, your problem is
fixed.  It should take you 2 mins tops to wire this up, so you have
very little to lose trying it.  I'm fine with being wrong (it happens
a lot, ask my wife), but if I were you, I wouldn't dismiss the idea
with "I don't think" since making sure is a simple exercise.

On Tue, Feb 10, 2015 at 8:24 AM, rsteppac2 <> wrote:
> 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:
> Sent from the Camel - Users mailing list archive at

View raw message