[
https://issues.apache.org/jira/browse/CAMEL-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510517#comment-13510517
]
Andrej Zachar commented on CAMEL-5815:
--------------------------------------
Hello Willem,
well, initially I did not expect that this patch would grow into this size.
Actually I have done more, but I didn't want to include it, it would be may be
too much to process at the beginning. So once you are done, I will send you
some additional features regarding wsa:replyTo response sender within a camel
route. But if you want it now, I can send it :)
Ad 1)
The ultimate receiver and actors+roles are done exactly like in Spring WS, e.g.
AbstractAddressingEndpointMapping.
So my new endpoint WSACamelEndpointMapping has this functionality out-of-box,
because it is inherited from the spring-ws's AbstractAddressingEndpointMapping.
The classical CamelEndpointMapping has the ultimate receiver and actorsOrRoles
propagated into
SoapEndpointInvocationChain(endpoint, interceptors, actorsOrRoles,
isUltimateReceiver);
That is all what was done regarding ultimate receiver and actors+roles.
Ad 2) Because I am working by TDD, I have done tests but a corresponding
functionality is still not developed. Initially I though that I will do it,
but I found some problems on the way that did not allow me to do it. If you
want I can discuss it with you, but for now, feel free to remove them!
I hope I have answered your questions.
Cheers,
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: 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
