[
https://issues.apache.org/jira/browse/SANDESHA2-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582550#action_12582550
]
David Illsley commented on SANDESHA2-125:
-----------------------------------------
OK, apparently according to the RSP (quoted below), the WCF behaviour is
correct.
"R0600 An RMS SHOULD use the same Sequence for all reliable response messages
(replies and faults) corresponding to all reliable request messages that shared
the same Sequence."
However, there are clearly special cases - mustUnderstand faults, some WS-RM
faults etc, and I'm not sure what they are, so I'm hesitant to just flip the
switch to enable reliable faults.
I'll follow up on this today, however at this point I'm tempted to delay this
until post 1.4.
> Interop issue with MS WCF using 'replay-model' / anonymous client - on
> application SoapFaults
> ---------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-125
> URL: https://issues.apache.org/jira/browse/SANDESHA2-125
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Axis2 1.3, Sandesha2 1.3 - interop testing with WCF 3.5
> Reporter: Hans G Knudsen
> Priority: Blocker
>
> SoapFaults donot get transferred correctly neither from
> Axis Service to .Net/WCF client nor
> .Net/WCF to Axis Service
> when SoapFaults are thrown at application level - in the RM Session...
> I seems that Axis relies on WS-A 'RelatesTo' to identify the the request and
> .Net/WCF relies on WS-RM <Sequence> information .
> I donot know what is the correct way...
> /hans
> ::: Axis
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";>
> <soapenv:Header>
>
> <wsa:Action>http://rep.oio.dk/oiosi.ehandel.gov.dk/xml/schemas/2007/09/01/InternalSystemFailureFault</wsa:Action>
> <wsa:RelatesTo>urn:uuid:F4DEBCE5673CF4144E1193386088801</wsa:RelatesTo>
> </soapenv:Header>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Receiver</soapenv:Value>
> <soapenv:Subcode>
> <soapenv:Value>soapenv:InternalSystemFailureFault</soapenv:Value>
> </soapenv:Subcode>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="da-DK">Service failed with complicated
> MainException : 42</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> :::: DOT NET
> <?xml version="1.0"?>
> <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:Sequence s:mustUnderstand="1">
> <r:Identifier>urn:uuid:6DAD31B8D6F3A43AF51193386168693</r:Identifier>
> <r:MessageNumber>1</r:MessageNumber>
> </r:Sequence>
> <r:SequenceAcknowledgement>
>
> <r:Identifier>urn:uuid:93c0d422-b008-4816-adcc-164975112be2</r:Identifier>
> <r:AcknowledgementRange Lower="1" Upper="1"/>
> </r:SequenceAcknowledgement>
> <a:Action s:mustUnderstand="1">*</a:Action>
> </s:Header>
> <s:Body>
> <s:Fault>
> <s:Code>
> <s:Value>s:Receiver</s:Value>
> <s:Subcode>
> <s:Value>s:InternalSystemFailureFault</s:Value>
> </s:Subcode>
> </s:Code>
> <s:Reason>
> <s:Text xml:lang="da-DK">Could not valdiate ...</s:Text>
> </s:Reason>
> </s:Fault>
> </s:Body>
> </s:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
