[
https://issues.apache.org/jira/browse/CAMEL-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510974#comment-13510974
]
Willem Jiang commented on CAMEL-5815:
-------------------------------------
Hi Andrej
As we are not plan to release the Camel 2.11.0 at the end of this year. I think
we could have some time to enhance this feature this month. I will try to
commit the patch today.
If you are using git, you can do the commit in some small step, and attache
them to the sub issue. It could make me more easier to digest the patches :)
Cheers,
Willem
> 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.11.0
> Reporter: Andrej Zachar
> Assignee: Willem Jiang
> Labels: patch
> Fix For: Future
>
> Attachments: camel-spring-ws-2.11.patch,
> camel-spring-ws-trunk-WS-Addressing-Support-IncludingTets.patch
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> 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
