You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Paul Fremantle <pz...@gmail.com> on 2007/03/20 19:29:00 UTC
wsa:MessageID required
I'm testing Axis2 against Microsoft .NET and its sending back a
message that includes a wsa:Action but not a wsa:MessageID. Its using
the
http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
In that spec, wsa:MessageID is optional. However, the addressing
module has the following check:
if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
String messageId = msgContext.getOptions().getMessageId();
if (messageId == null || "".equals(messageId)) {
AddressingFaultsHelper
.triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
}
}
which is happening in my case because the operation is IN-OUT.
Can anyone explain why we are insisting on wsa:MessageID?
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by David Illsley <da...@gmail.com>.
Section 3.4.1 -
http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#formreplymsg
David
On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> David
>
> This fault is happening in the Axis2 client.
>
> Can you please point me at the requirement in the spec? I don't see it.
>
> Thanks
> Paul
>
> On 3/20/07, David Illsley <da...@gmail.com> wrote:
> > Hi Paul,
> >
> > The why is that it's an addressing spec requirement for request
> > messages of a 2-way MEP (something which surprises a lot of people,
> > you're not the first person I've spoken to about this today)
> >
> > I'm not clear how you have an IN-OUT operation which receives response
> > messages? That code is intended to allow a null message id on one-way
> > and response messages... I'm not sure why it's not working.
> >
> > David
> >
> > On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > > I'm testing Axis2 against Microsoft .NET and its sending back a
> > > message that includes a wsa:Action but not a wsa:MessageID. Its using
> > > the
> > > http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
> > >
> > > http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
> > >
> > > In that spec, wsa:MessageID is optional. However, the addressing
> > > module has the following check:
> > >
> > > if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> > > mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> > > mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> > > String messageId = msgContext.getOptions().getMessageId();
> > > if (messageId == null || "".equals(messageId)) {
> > > AddressingFaultsHelper
> > >
> > > .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> > > }
> > > }
> > >
> > > which is happening in my case because the operation is IN-OUT.
> > >
> > > Can anyone explain why we are insisting on wsa:MessageID?
> > >
> > > Paul
> > > --
> > > Paul Fremantle
> > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > >
> > > http://bloglines.com/blog/paulfremantle
> > > paul@wso2.com
> > >
> > > "Oxygenating the Web Service Platform", www.wso2.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > David Illsley - IBM Web Services Development
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by Paul Fremantle <pz...@gmail.com>.
I guess its actually a bug in Sandesha2 :-)
Sorry to have bothered you and thanks for the help.
Paul
On 3/20/07, David Illsley <da...@gmail.com> wrote:
> Urgh. So.. if the first TerminateSequence is a one-way, why is the
> AxisOperation for TerminateSequence not IN-ONLY?
> David
>
>
> On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > Let me add this is happening in a Sandesha2 flow.
> > In fact its a little odd situation. Basically there is a one-way
> > operation (TerminateSequence) and "piggybacked" on the response flow
> > is another TerminateSequence. So in fact its two one-ways happening as
> > an HTTP request response.
> >
> > Here is the message causing the problem:
> >
> > <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
> > xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm"
> > xmlns:a="http://www.w3.org/2005/08/addressing">
> > <s:Header>
> > <r:SequenceAcknowledgement>
> > <r:Identifier>urn:uuid:495c4583-818f-453d-8837-135ba21f172c</r:Identifier>
> > <r:AcknowledgementRange Lower="1" Upper="1"/>
> > <netrm:BufferRemaining
> > xmlns:netrm="http://schemas.microsoft.com/ws/2006/05/rm">8</netrm:BufferRemaining>
> > </r:SequenceAcknowledgement>
> > <a:Action
> > s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence</a:Action>
> > </s:Header>
> > <s:Body>
> > <r:TerminateSequence>
> > <r:Identifier>urn:uuid:A1294295A53C61C4931174412901305</r:Identifier>
> > </r:TerminateSequence>
> > </s:Body></s:Envelope>
> >
> > Here is the stack trace if you are interested:
> >
> > org.apache.axis2.AxisFault: A required header representing a Message
> > Addressing Property is not present
> > at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:572)
> > at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:329)
> > at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> > at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> > at java.lang.Thread.run(Unknown Source)
> > Caused by: org.apache.axis2.AxisFault: A required header representing
> > a Message Addressing Property is not present
> > at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:346)
> > at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:275)
> > at org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:160)
> > at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:50)
> > at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
> > at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:565)
> >
> >
> > And here is the message.
> >
> > On 3/20/07, Paul Fremantle <pz...@gmail.com> wrote:
> > > David
> > >
> > > This fault is happening in the Axis2 client.
> > >
> > > Can you please point me at the requirement in the spec? I don't see it.
> > >
> > > Thanks
> > > Paul
> > >
> > > On 3/20/07, David Illsley <da...@gmail.com> wrote:
> > > > Hi Paul,
> > > >
> > > > The why is that it's an addressing spec requirement for request
> > > > messages of a 2-way MEP (something which surprises a lot of people,
> > > > you're not the first person I've spoken to about this today)
> > > >
> > > > I'm not clear how you have an IN-OUT operation which receives response
> > > > messages? That code is intended to allow a null message id on one-way
> > > > and response messages... I'm not sure why it's not working.
> > > >
> > > > David
> > > >
> > > > On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > > > > I'm testing Axis2 against Microsoft .NET and its sending back a
> > > > > message that includes a wsa:Action but not a wsa:MessageID. Its using
> > > > > the
> > > > > http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
> > > > >
> > > > > http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
> > > > >
> > > > > In that spec, wsa:MessageID is optional. However, the addressing
> > > > > module has the following check:
> > > > >
> > > > > if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> > > > > mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> > > > > mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> > > > > String messageId = msgContext.getOptions().getMessageId();
> > > > > if (messageId == null || "".equals(messageId)) {
> > > > > AddressingFaultsHelper
> > > > >
> > > > > .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> > > > > }
> > > > > }
> > > > >
> > > > > which is happening in my case because the operation is IN-OUT.
> > > > >
> > > > > Can anyone explain why we are insisting on wsa:MessageID?
> > > > >
> > > > > Paul
> > > > > --
> > > > > Paul Fremantle
> > > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > > > >
> > > > > http://bloglines.com/blog/paulfremantle
> > > > > paul@wso2.com
> > > > >
> > > > > "Oxygenating the Web Service Platform", www.wso2.com
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > David Illsley - IBM Web Services Development
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Paul Fremantle
> > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > >
> > > http://bloglines.com/blog/paulfremantle
> > > paul@wso2.com
> > >
> > > "Oxygenating the Web Service Platform", www.wso2.com
> > >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> David Illsley - IBM Web Services Development
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by David Illsley <da...@gmail.com>.
Urgh. So.. if the first TerminateSequence is a one-way, why is the
AxisOperation for TerminateSequence not IN-ONLY?
David
On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> Let me add this is happening in a Sandesha2 flow.
> In fact its a little odd situation. Basically there is a one-way
> operation (TerminateSequence) and "piggybacked" on the response flow
> is another TerminateSequence. So in fact its two one-ways happening as
> an HTTP request response.
>
> Here is the message causing the problem:
>
> <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
> xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm"
> xmlns:a="http://www.w3.org/2005/08/addressing">
> <s:Header>
> <r:SequenceAcknowledgement>
> <r:Identifier>urn:uuid:495c4583-818f-453d-8837-135ba21f172c</r:Identifier>
> <r:AcknowledgementRange Lower="1" Upper="1"/>
> <netrm:BufferRemaining
> xmlns:netrm="http://schemas.microsoft.com/ws/2006/05/rm">8</netrm:BufferRemaining>
> </r:SequenceAcknowledgement>
> <a:Action
> s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence</a:Action>
> </s:Header>
> <s:Body>
> <r:TerminateSequence>
> <r:Identifier>urn:uuid:A1294295A53C61C4931174412901305</r:Identifier>
> </r:TerminateSequence>
> </s:Body></s:Envelope>
>
> Here is the stack trace if you are interested:
>
> org.apache.axis2.AxisFault: A required header representing a Message
> Addressing Property is not present
> at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:572)
> at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:329)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.apache.axis2.AxisFault: A required header representing
> a Message Addressing Property is not present
> at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:346)
> at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:275)
> at org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:160)
> at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:50)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
> at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:565)
>
>
> And here is the message.
>
> On 3/20/07, Paul Fremantle <pz...@gmail.com> wrote:
> > David
> >
> > This fault is happening in the Axis2 client.
> >
> > Can you please point me at the requirement in the spec? I don't see it.
> >
> > Thanks
> > Paul
> >
> > On 3/20/07, David Illsley <da...@gmail.com> wrote:
> > > Hi Paul,
> > >
> > > The why is that it's an addressing spec requirement for request
> > > messages of a 2-way MEP (something which surprises a lot of people,
> > > you're not the first person I've spoken to about this today)
> > >
> > > I'm not clear how you have an IN-OUT operation which receives response
> > > messages? That code is intended to allow a null message id on one-way
> > > and response messages... I'm not sure why it's not working.
> > >
> > > David
> > >
> > > On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > > > I'm testing Axis2 against Microsoft .NET and its sending back a
> > > > message that includes a wsa:Action but not a wsa:MessageID. Its using
> > > > the
> > > > http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
> > > >
> > > > http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
> > > >
> > > > In that spec, wsa:MessageID is optional. However, the addressing
> > > > module has the following check:
> > > >
> > > > if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> > > > mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> > > > mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> > > > String messageId = msgContext.getOptions().getMessageId();
> > > > if (messageId == null || "".equals(messageId)) {
> > > > AddressingFaultsHelper
> > > >
> > > > .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> > > > }
> > > > }
> > > >
> > > > which is happening in my case because the operation is IN-OUT.
> > > >
> > > > Can anyone explain why we are insisting on wsa:MessageID?
> > > >
> > > > Paul
> > > > --
> > > > Paul Fremantle
> > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > > >
> > > > http://bloglines.com/blog/paulfremantle
> > > > paul@wso2.com
> > > >
> > > > "Oxygenating the Web Service Platform", www.wso2.com
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > David Illsley - IBM Web Services Development
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by Paul Fremantle <pz...@gmail.com>.
Let me add this is happening in a Sandesha2 flow.
In fact its a little odd situation. Basically there is a one-way
operation (TerminateSequence) and "piggybacked" on the response flow
is another TerminateSequence. So in fact its two one-ways happening as
an HTTP request response.
Here is the message causing the problem:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm"
xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<r:SequenceAcknowledgement>
<r:Identifier>urn:uuid:495c4583-818f-453d-8837-135ba21f172c</r:Identifier>
<r:AcknowledgementRange Lower="1" Upper="1"/>
<netrm:BufferRemaining
xmlns:netrm="http://schemas.microsoft.com/ws/2006/05/rm">8</netrm:BufferRemaining>
</r:SequenceAcknowledgement>
<a:Action
s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence</a:Action>
</s:Header>
<s:Body>
<r:TerminateSequence>
<r:Identifier>urn:uuid:A1294295A53C61C4931174412901305</r:Identifier>
</r:TerminateSequence>
</s:Body></s:Envelope>
Here is the stack trace if you are interested:
org.apache.axis2.AxisFault: A required header representing a Message
Addressing Property is not present
at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:572)
at org.apache.sandesha2.workers.SenderWorker.run(SenderWorker.java:329)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.axis2.AxisFault: A required header representing
a Message Addressing Property is not present
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:346)
at org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:275)
at org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:160)
at org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:50)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
at org.apache.sandesha2.workers.SenderWorker.checkForSyncResponses(SenderWorker.java:565)
And here is the message.
On 3/20/07, Paul Fremantle <pz...@gmail.com> wrote:
> David
>
> This fault is happening in the Axis2 client.
>
> Can you please point me at the requirement in the spec? I don't see it.
>
> Thanks
> Paul
>
> On 3/20/07, David Illsley <da...@gmail.com> wrote:
> > Hi Paul,
> >
> > The why is that it's an addressing spec requirement for request
> > messages of a 2-way MEP (something which surprises a lot of people,
> > you're not the first person I've spoken to about this today)
> >
> > I'm not clear how you have an IN-OUT operation which receives response
> > messages? That code is intended to allow a null message id on one-way
> > and response messages... I'm not sure why it's not working.
> >
> > David
> >
> > On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > > I'm testing Axis2 against Microsoft .NET and its sending back a
> > > message that includes a wsa:Action but not a wsa:MessageID. Its using
> > > the
> > > http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
> > >
> > > http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
> > >
> > > In that spec, wsa:MessageID is optional. However, the addressing
> > > module has the following check:
> > >
> > > if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> > > mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> > > mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> > > String messageId = msgContext.getOptions().getMessageId();
> > > if (messageId == null || "".equals(messageId)) {
> > > AddressingFaultsHelper
> > >
> > > .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> > > }
> > > }
> > >
> > > which is happening in my case because the operation is IN-OUT.
> > >
> > > Can anyone explain why we are insisting on wsa:MessageID?
> > >
> > > Paul
> > > --
> > > Paul Fremantle
> > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> > >
> > > http://bloglines.com/blog/paulfremantle
> > > paul@wso2.com
> > >
> > > "Oxygenating the Web Service Platform", www.wso2.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > David Illsley - IBM Web Services Development
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by Paul Fremantle <pz...@gmail.com>.
David
This fault is happening in the Axis2 client.
Can you please point me at the requirement in the spec? I don't see it.
Thanks
Paul
On 3/20/07, David Illsley <da...@gmail.com> wrote:
> Hi Paul,
>
> The why is that it's an addressing spec requirement for request
> messages of a 2-way MEP (something which surprises a lot of people,
> you're not the first person I've spoken to about this today)
>
> I'm not clear how you have an IN-OUT operation which receives response
> messages? That code is intended to allow a null message id on one-way
> and response messages... I'm not sure why it's not working.
>
> David
>
> On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> > I'm testing Axis2 against Microsoft .NET and its sending back a
> > message that includes a wsa:Action but not a wsa:MessageID. Its using
> > the
> > http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
> >
> > http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
> >
> > In that spec, wsa:MessageID is optional. However, the addressing
> > module has the following check:
> >
> > if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> > mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> > mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> > String messageId = msgContext.getOptions().getMessageId();
> > if (messageId == null || "".equals(messageId)) {
> > AddressingFaultsHelper
> >
> > .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> > }
> > }
> >
> > which is happening in my case because the operation is IN-OUT.
> >
> > Can anyone explain why we are insisting on wsa:MessageID?
> >
> > Paul
> > --
> > Paul Fremantle
> > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >
> > http://bloglines.com/blog/paulfremantle
> > paul@wso2.com
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> David Illsley - IBM Web Services Development
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: wsa:MessageID required
Posted by David Illsley <da...@gmail.com>.
Hi Paul,
The why is that it's an addressing spec requirement for request
messages of a 2-way MEP (something which surprises a lot of people,
you're not the first person I've spoken to about this today)
I'm not clear how you have an IN-OUT operation which receives response
messages? That code is intended to allow a null message id on one-way
and response messages... I'm not sure why it's not working.
David
On 20/03/07, Paul Fremantle <pz...@gmail.com> wrote:
> I'm testing Axis2 against Microsoft .NET and its sending back a
> message that includes a wsa:Action but not a wsa:MessageID. Its using
> the
> http://www.w3.org/2005/08/addressing namespace, which dereferences to this spec:
>
> http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/
>
> In that spec, wsa:MessageID is optional. However, the addressing
> module has the following check:
>
> if (mepConstant == WSDLConstants.MEP_CONSTANT_IN_OUT ||
> mepConstant == WSDLConstants.MEP_CONSTANT_IN_OPTIONAL_OUT ||
> mepConstant == WSDLConstants.MEP_CONSTANT_ROBUST_IN_ONLY) {
> String messageId = msgContext.getOptions().getMessageId();
> if (messageId == null || "".equals(messageId)) {
> AddressingFaultsHelper
>
> .triggerMessageAddressingRequiredFault(msgContext, WSA_MESSAGE_ID);
> }
> }
>
> which is happening in my case because the operation is IN-OUT.
>
> Can anyone explain why we are insisting on wsa:MessageID?
>
> Paul
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org