[
https://issues.apache.org/jira/browse/CAMEL-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490491#comment-13490491
]
Andrej Zachar commented on CAMEL-5724:
--------------------------------------
Hi!
In the mean time I have also found few issues.
1. The method createEndpoint in SpringWebserviceComponent needs to updated. The
order of calling methods needs to be changed as follows
configureMessageFilter(parameters, configuration);
setProperties(configuration, parameters);
instead of
setProperties(configuration, parameters);
configureMessageFilter(parameters, configuration);
Otherwise messageFilter parameter from the endpoint URI is removed before it is
processed.
2. Bad spelling
Also there is one bad spelling in the class BasicFilterStrategy instead of
processHeaderAndAttachemtns should be processHeaderAndAttachments.
As I said I am working on tests and doc. I will let you know, when it will be
ready.
Cheers,
Andrej
> 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.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
