Please add the note about SOAP Fault, Doug Bunting proposed. It is important for interoperability. > Date: Fri, 16 Nov 2001 10:24:08 -0500 > From: Christopher Ferris <
chris.ferris@sun.com> > Subject: Re: Fw: [ebxml-msg] Re: SOAP Fault location > To: Doug Bunting <
dougb62@yahoo.com> > Cc: ebXML Messaging (E-mail) <
ebxml-msg@lists.oasis-open.org> > Message-id: <
3BF52F98.9080007@sun.com > > > +1, we cannot mandate what happens at the SOAP processor level. > > Doug Bunting wrote: > > 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 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