[
https://issues.apache.org/jira/browse/ODE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518876
]
richt edited comment on ODE-154 at 8/9/07 4:44 PM:
------------------------------------------------------------
Hi Matthieu, I'll start by saying that I'm not an expert at reading the WS-*
specs.
The code that I'm calling into which validates the WS-Addressing header is
actually in-house (I was previously under the impression this was third party
code, it's not). That said, this validation code does intend to properly
implement the spec, so we just need to iron out where the adjustments need to
be made.
In reading the spec, it's my understanding that the To and Action headers are
the only "required" headers in the simplest case. However if a reply is
expected from the call, then the ReplyTo and MessageID headers must be in the
request message.
>From section 3.1 of the spec, in regards to ReplyTo and MessageID
>(http://www.w3.org/Submission/ws-addressing/#_Toc77464323):
/wsa:ReplyTo - "This element MUST be present if a reply is expected. If this
element is present, wsa:MessageID MUST be present."
What are your thoughts on that, am I misinterpreting that?
I can get the implementors of this in-house code to try and back off on
validation, but I'm wondering if other full WS-Addressing implementations won't
have the same issue when receiving calls from Ode?
I'm also somewhat under the impression that some if not all of this should be
handled by Axis2. Is there someone from the Axis2 crowd that can confirm that
Ode actually needs to be adding the headers itself?
Thanks!!
was (Author: richt):
Hi Matthieu, I'll start by saying that I'm not an expert at reading the
WS-* specs.
The code that I'm calling into which validates the WS-Addressing header is
actually in-house (I was previously under the impression this was third party
code, it's not). That said, this validation code does intend to properly
implement the spec, so we just need to iron out where the adjustments need to
be made.
In reading the spec, it's my understanding that the To and Action headers are
the only "required" headers in the simplest case. However if a reply is
expected from the call, then the ReplyTo and MessageID headers must be in the
request message.
>From section 3.1 of the spec, in regards to ReplyTo and MessageID
>(http://www.w3.org/Submission/ws-addressing/#_Toc77464322):
/wsa:ReplyTo - "This element MUST be present if a reply is expected. If this
element is present, wsa:MessageID MUST be present."
What are your thoughts on that, am I misinterpreting that?
I can get the implementors of this in-house code to try and back off on
validation, but I'm wondering if other full WS-Addressing implementations won't
have the same issue when receiving calls from Ode?
I'm also somewhat under the impression that some if not all of this should be
handled by Axis2. Is there someone from the Axis2 crowd that can confirm that
Ode actually needs to be adding the headers itself?
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.
