[
https://issues.apache.org/jira/browse/ODE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520630
]
Richard Taylor commented on ODE-154:
------------------------------------
I'm going to attach an additional patch (wsa.patch) that primarily does the
following:
1. Adds the values of ReplyTo and MessageID to the outgoing soap headers. It
only does this only if the MEP is Request/Response.
2. Adds support for extracting the WS-Addressing "Action" from the port
definition in the WSDL, in addition to the soap binding. When searching for
the "Action" it first looks for a wsaw:Action in the portType definition, then
it falls back to the original SOAPAction in the binding definition. See [1]
for more information
This isn't adding complete WS-Addressing support but it is a step closer. Ode
should consider taking advantage of the Axis2 "Addressing" module in the
future, if feasible.
[1] http://www.w3.org/TR/ws-addr-wsdl/#explicitaction
> Missing WS-Addressing "MessageID" header when invoking a WSA compliant
> external services
> ----------------------------------------------------------------------------------------
>
> Key: ODE-154
> URL: https://issues.apache.org/jira/browse/ODE-154
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 1.1
> Environment: JDK 1.5.0_11
> Axis2 Distribution
> WinXP x64
> Reporter: Richard Taylor
> Assignee: Matthieu Riou
> Fix For: 1.1
>
>
> When I try to invoke an external service that implements WS-Addressing, I get
> an error returned saying "A required header representing a Message Addressing
> Property is not present." The header it is referring to is "wsa:MessageID".
> Ode properly sends the wsa:To and wsa:Action headers, but apparently not the
> MessageID. The missing header was confirmed using TCPMon
> It is possible that a MessageID is properly inserted when using BPEL
> Correlation IDs or something along those lines, in other words this may be a
> user error. But I could not find any mention of it in Ode documentation.
> Nor could I find the the proper method call to Options.setMessageId() in the
> source code while setting up the outgoing message.
> The issue appears to be somewhere in the area of
> org.apache.ode.axis2.ExternalService.invoke(). I believe we should be
> calling options.setMessageId() somewhere in there.
> I'm not sure if this affects the JBI distribution as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
