[
https://issues.apache.org/jira/browse/ODE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518855
]
Matthieu Riou commented on ODE-154:
-----------------------------------
I've been looking at the WS-Addressing spec and the MessageID element is
optional, which explains why we don't send it. We actually don't need it of
care about its eventual presence.
So what type of service are you invoking? Do you know it uses a specific web
service layer? If there's a real interoperability issue because of this missing
element then we can add it but if it's just one partly broken implementation,
then adding it could break others...
Thanks!
> 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.
