You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Damian (Commented) (JIRA)" <ji...@apache.org> on 2011/11/03 00:49:32 UTC

[jira] [Commented] (CAMEL-4515) Spring-WS should populate Camel Header with the SOAP Header

    [ https://issues.apache.org/jira/browse/CAMEL-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142696#comment-13142696 ] 

Damian commented on CAMEL-4515:
-------------------------------

I took out the populating of the headers as I thought that it would be more consistent to have one way of writing/reading headers. On reflection it reduces the usability so I've put that back in. What are your thoughts on setting the Exchange Header? Should it be a collection of Source or maybe a single Source from the header level? I've implemented the latter.

I've modified the transformation to use a static XmlConverter. Is this the correct way to use this?

Attached is an updated patch.
                
> Spring-WS should populate Camel Header with the SOAP Header
> -----------------------------------------------------------
>
>                 Key: CAMEL-4515
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4515
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-ws
>    Affects Versions: 2.8.1
>            Reporter: Damian
>            Priority: Minor
>         Attachments: CAMEL-4515.1.patch, CAMEL-4515.1.patch, CAMEL-4515.2.patch, CAMEL-4515.patch
>
>
> Currently the Camel-Spring-WS component does not support the setting of SOAP Headers and has issues getting them. The current issue getting the SOAP Headers when receiving a message is that the resulting header key includes the namespace.
> Change the component so that a Camel header "CamelSpringWebserviceSoapHeader" can be populated with an intended SOAP Header for a request, and that this Header is also populated from the SOAP Header on a response.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira