[ODE-154] Missing WS-Addressing "MessageID" header when invoking a WSA compliant external services

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1
• Fix Version/s: 1.1
• Component/s: Axis2 Integration
• Environment: JDK 1.5.0_11; Axis2 Distribution; WinXP x64
• Assignee: Matthieu Riou
• Reporter: Richard Taylor
• Created: 13/Jul/07 19:29
• Updated: 17/Aug/07 21:43
• Resolved: 10/Aug/07 00:36

Description

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.