[
https://issues.apache.org/jira/browse/CAMEL-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643738#comment-13643738
]
Andrej Zachar commented on CAMEL-5815:
--------------------------------------
Hello Clause,
I had created it a long time ago, but because of some legal issues related to
publishing via apache wiki it was not resolved.
Here is missing documentation:
I hope you will get it!
Best regards,
Andrej
> 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: 2.11.0
>
> Attachments: camel-spring-ws-2.11.patch,
> camel-spring-ws-replyTo-usingCamelAgain.patch,
> camel-spring-ws-replyTo-usingCamelAgain.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
