[
https://issues.apache.org/jira/browse/CAMEL-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482285#comment-13482285
]
Andrej Zachar edited comment on CAMEL-5724 at 10/23/12 12:26 PM:
-----------------------------------------------------------------
Hi Wilem,
I guess that as the same way as you suggest to handle the header support can be
handled an attachment one. E.g. attachments beside headers are not passed from
the Exchange instance into the WebServiceMessage [1][2].
Therefore I suggest to create a new endpoint param called "filterFactory" were
you can provide a filter (for instance a sprig bean) that will filter
WebServiceMessage in SpringWebserviceConsumer [1] and SpringWebserviceProducer
[2] in order to provide exchange data into spring's WebServiceMessage.
Than for example will be very easy to provide MTOM attachments support or just
a simple text attachments support.
I am actually working on this solution, thus I can provide you patch if you are
interested. Only problem what I see how to test it.
You know, your current test suites contain tests suitable for testing of
Exchange's results, nor WebServiceMessage results.
That is why the test consumeStockQuoteWebserviceInOnly [3] is working even
though there is no real implementation of the headers processing. For instance
header foo is obtained from exchange only!
[1]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/main/java/org/apache/camel/component/spring/ws/SpringWebserviceConsumer.java
[2]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/main/java/org/apache/camel/component/spring/ws/SpringWebserviceProducer.java
[3]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/test/java/org/apache/camel/component/spring/ws/ProducerLocalRouteTest.java
Best regards,
Andrej
was (Author: azachar):
Hi Wilem,
I guess that as the same way as you suggest to handle header support can be
handled an attachment one. E.g. attachments beside headers are not passed from
the Exchange instance into the WebServiceMessage [1][2].
Therefore I suggest to create a new endpoint param called "filterFactory" were
you can provide a filter (for instance a sprig bean) that will filter
WebServiceMessage in SpringWebserviceConsumer [1] and SpringWebserviceProducer
[2] in order to provide exchange data into spring's WebServiceMessage.
Than for example will be very easy to provide MTOM attachments support or just
a simple text attachments support.
I am actually working on this solution, thus I can provide you patch if you are
interested. Only problem what I see how to test it.
You know, your current test suites contain tests suitable for testing of
Exchange's results, nor WebServiceMessage results.
That is why the test consumeStockQuoteWebserviceInOnly [3] is working even
though there is no real implementation of the headers processing. For instance
header foo is obtained from exchange only!
[1]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/main/java/org/apache/camel/component/spring/ws/SpringWebserviceConsumer.java
[2]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/main/java/org/apache/camel/component/spring/ws/SpringWebserviceProducer.java
[3]
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.1/components/camel-spring-ws/src/test/java/org/apache/camel/component/spring/ws/ProducerLocalRouteTest.java
Best regards,
Andrej
> Spring-WS consumer and producer do not propagate any custom header 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
> Labels: patch
> Fix For: 2.10.3, 2.11.0
>
> Attachments: camel-spring-ws.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
