[ 
https://issues.apache.org/jira/browse/CAMEL-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Babak Vahdat reopened CAMEL-5724:
---------------------------------


Willem, for the third time I'm kindly asking you to update the Wiki for this 
ticket as this JIRA has been assigned to you. If for whatever reason you can't 
or don't want to do this, then please let me know so I'll do it as IMHO it's 
*very* important to keep the code base in sync with it's documentation so ppl 
are aware of the latest and greatest features. For this purpose now I'm 
reopening this ticket. Thanks!
                
> Spring-WS consumer and producer do not propagate some custome headers and 
> attachements to a response message
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5724
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5724
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-ws
>    Affects Versions: 2.10.1
>            Reporter: Andrej Zachar
>            Assignee: Willem Jiang
>              Labels: patch
>             Fix For: 2.10.3, 2.11.0
>
>         Attachments: 
> camel-spring-ws-headerAndAttachmentSupportIncludingTests-branch-2.10.1.patch, 
> camel-spring-ws.patch, headerAndAttachmentsSupport.patch
>
>
> Hi!
> I wanted to send back as response or as a request some soap messages with 
> modified header.
> I found out that SpringWebserviceProducer and SpringWebserviceConsumer do not 
> populate a soap header for any outgoing message from a camel exchange.
> In the attachments I am sending you a patch against camel-spring-ws 2.10.1 
> that solves this issue.
> Please let me know, what do you think about it.
> Best regards,
> Andrej
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to