[
https://issues.apache.org/jira/browse/CAMEL-8351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890880#comment-15890880
]
ASF GitHub Bot commented on CAMEL-8351:
---------------------------------------
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1499
CAMEL-8351 - simple implementation for breadcrumbId to be set as camel
exhange's header
simple implementation, if mimeheaders may have multiple values as string
array for breadcrumbs header, breadcrumb generation strategy may need to be
implemented and this may require a config uri param on the endpoint to inject
such strategy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/onders86/camel CAMEL-8351
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1499.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1499
----
commit 0967cd8b298429be85de6d01c79ccd57af293864
Author: onders86 <[email protected]>
Date: 2017-03-01T19:17:28Z
CAMEL-8351 - simple implementation for breadcrumbId to be set as camel
exhange's header
commit 8af371fefc910c63b3850f798028041e4fbe5089
Author: onders86 <[email protected]>
Date: 2017-03-01T19:22:23Z
CAMEL-8351 - simple implementation for breadcrumbId to be set as camel
exhange's header
----
> Spring-ws consumer ignores breadcrumbId http header
> ---------------------------------------------------
>
> Key: CAMEL-8351
> URL: https://issues.apache.org/jira/browse/CAMEL-8351
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
> Affects Versions: 2.14.1
> Reporter: Ralf Steppacher
> Assignee: onder sezgin
>
> The spring-ws consumer does not pick up a {{breadcrumbId}} HTTP header. I
> tried to find a hook where I could jump in and make the breadcrumbId from the
> HTTP headers available, but could not find any.
> The spring-ws endpoint ({{SpringWebserviceConsumer}}) does not care about
> HTTP headers, only about SOAP headers and properties of the
> {{org.springframework.ws.context.MessageContext}}. SOAP headers get converted
> into exchange headers while message context properties get converted into
> exchange properties. Properties could be added by using a
> {{org.springframework.ws.server.EndpointInterceptor}}.
> A breadcrumbId property is not picked up by Camel though. The
> {{org.apache.camel.impl.DefaultUnitOfWork}} creates a new breadcrumbId
> because it only checks the headers of the in-message, not the exchange
> properties for an already existing breadcrumb ID.
> A SOAPHeader "breadcrumbId" is copied over to the in-message headers and
> picked up by the DefaultUnitOfWork, but it is not automagically converted
> from {{org.springframework.ws.soap.saaj.SaajSoapHeaderElement}} to its text
> content.
> Ideally the web service consumer would pick up the breadcrumId (and others)
> from the HTTP headers and restore them as in-message headers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
