[
https://issues.apache.org/jira/browse/ODE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518880
]
Matthieu Riou commented on ODE-154:
-----------------------------------
Good point, ODE is at fault here. We actually didn't consider the inclusion of
the ReplyTo for request/response message exchange patterns. So for those
patterns (and not for one ways) we'll provide both the ReplyTo and the
MessageID element. Note that in that case, the ReplyTo will be set to the
anonymous URL defined by ws-addressing as we're on HTTP and the same transport
connection is used.
About Axis2, they have a WS-Addressing implementation but we can't reuse it as
we're extending the WS-Addressing headers for the callback mechanisms. Actually
the Axis2 WS-Addressing was even broken on 1.1 but now that we've upgraded we
might want to check that again. But that's another story.
Thanks for pointing out the issue.
> 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
> 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.
