|
How about a non-normative note:
Note: A SOAP Fault element on its own may not provide the
requesting MSH with the context necessary to identify the message in
error. An MSH returning a SOAP Fault should include ebXML MessageHeader
and ErrorList SOAP extensions in the same SOAP message. This would be
especially useful when the error is returned
asynchronously.
We can't require this because we can't mandate what
errors are caught by the SOAP processor prior to invocation of the ebXML
handler.
does this help?
doug
----- Original Message -----
Sent: Wednesday, 14 November 2001
23:28
Subject: Re: Fw: [ebxml-msg] Re: SOAP Fault
location
I know putting RefMessageId in the SOAP Fault
message is NOT precluded.
However, if it's not required to do so, there is
no way to realize interoperability
between different implementations. I think spec
should describe how to do that.
I'm not sure which we should say whether "SOAP
Fault MUST include ebXML
MessageHeader" or "SOAP Fault SHOULD include
ebXML MessageHeader".
There might be discussion on this including other
possible resolution.
Thanks,
Iwasa
----- Original Message -----
Sent: Tuesday, November 13, 2001
5:13 AM
Subject: Re: Fw: [ebxml-msg] Re:
SOAP Fault location
There is no reason why a SOAP Fault message cannot include
the
ebXML MessageHeader SOAP extension header(s) to identify the
context
of the fault. The SOAP Fault message is only a description of what is
REQUIRED in a SOAP Fault, it is not limited to just an empty envelope
with a SOAP-ENV:Fault element.
Cheers,
Chris
iwasa
wrote:
009e01c16bf1$6ea45b80$d960a485@iwasalaptop type="cite">Arvola,
I think this is an error handling issue. Please put this on the issue list.
SOAP message/Fault does not have messageID/Reference message ID,
so ebXML can't identify the message from SOAP Fault message.
Thanks,
Iwasa
I received a question about SOAP Faults and ebXML Error from a developer.
Q1. When receiver side MSH returns an error condition to sender side MSH,
can the receiver side MSH send both ebXML Error and SOAP Fault using
one HTTP response (or one separate HTTP request in asynchronous mode)
at same time ?
I guess the answer to the question is "No".
Q2. The ebXML Message Service spec says:
"When asynchronous mode of message exchange is being used, a
HTTP response code in the range 2xx MUST be returned when the
message is received successfully and any error conditions
(including SOAP errors) must be returned via a separate HTTP
Post." (on P65 in v1.05)
However if answer to the Q1 above is "No", when sender side MSH
received a SOAP Fault by a separate HTTP POST in asynchronous mode,
how the sender side MSH know that which sen
t messages's error is
indicated by the SOAP Fault? SOAP Fault itself has not
RefToMessageId element...
Regards,
--
SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>
TEL:+81-45-476-4590(ext.7128-4241) FAX:+81-45-476-4726(ext.7128-6783)
Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
|