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

Claus Ibsen commented on CAMEL-5815:
------------------------------------

We apply patches on trunk, and then backport to previous branches. So your 
attached patch should be applied on trunk first, and then we backport that to 
the 2.10 branch. Though as the difference between trunk and 2.10 branch of 
spring-ws probably is identical, then your work against 2.10 should be fairly 
easy to apply on trunk.

                
> camel-spring-ws - Support for WS-Addressing Action
> --------------------------------------------------
>
>                 Key: CAMEL-5815
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5815
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-spring-ws
>    Affects Versions: 2.10.1
>            Reporter: Andrej Zachar
>            Assignee: Andrej Zachar
>              Labels: patch
>             Fix For: Future
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The camel spring-ws consumer doesn't currently support the WS-Addressing 
> Action and camel cannot dispatch such a message properly. There is only one 
> workaround available using a xpath, which is not a very straight forward 
> solution.
> Based on my previous experience with the patch for attachments and headers I 
> would like to implement this functionality.
> Please let me know if you have any comments or ideas that are left.
> In the solution I would like to implement a new universal endpoint mapping 
> key:
> action 
> which will act as the same as the key soapaction but it will add also a 
> possibility to retrieve action from soap wsa:action header instead of current 
> http SOAPAction.
> BTW: Are there any ideas how should be supported wsa:replyTo inside the 
> camel-spring-ws or how should be supported other attributes of WS-Addressing?
> Cheers,
> 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