[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrm] FAULTS IN WS-RELIABILITY
Paolo, An issue (REL-46) already exists for the same. As per my AI, I've already sent an proposal. http://lists.oasis-open.org/archives/wsrm/200307/msg00073.html -Sunil Paolo Romano wrote: > SOAP 1.1, section 4.4 SOAP FAULT states: > "... > detail > The detail element is intended for carrying application specific error > information related to the Body element. It MUST be present if the contents of > the Body element could not be successfully processed. It MUST NOT be used to > carry information about error information belonging to header entries. Detailed > error information belonging to header entries MUST be carried within header > entries. > > The absence of the detail element in the Fault element indicates that the fault > is not related to processing of the Body element. This can be used to > distinguish whether the Body element was processed or not in case of a fault > situation. > ..." > > --- > > In WS-RELIABILITY, example 3 pag.11-12, detail element is used to refer error > information concerning an invalid header. > If I do not misunderstand section 4.4 of SOAP 1.1, a SOAP fault should still be > raised in case of troubles with headers (and placed in the body), but a detailed > description of the problem should be provided somewhere else in the header, > while the body should not contain any detail, but only faultcode, faultstring and > possibly faultactor attribute. > > I copy the referenced ws-rm example. > > WS-RELIABILITY, pag.11-12: > <?xml version=”1.0”?> > <SOAP:Envelope > xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" > SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> > <SOAP:Header> > <rm:MessageHeader xmlns:rm=”http://schemas.fujitsu.com/rm” > SOAP:mustUnderstand=”1”> > <rm:MessageId>20020907-045261-0450@anyuri.com</rm:MessageId> > <rm:Timestamp>2002-09-07T10:10:07</rm:Timestamp> > </rm:MessageHeader> > <rm:RMResponse xmlns:rm=”http://schemas.fujitsu.com/rm” > SOAP:mustUnderstand=”1”> > <rm:MessageType>Fault</rm:MessageType> > <rm:RefToMessageId>20020907-12-34@anyuri.com</rm:RefToMessageId> > </rm:RMResponse> > </SOAP:Header> > > <SOAP:Body> > <SOAP:Fault> > <faultcode>SOAP:Client</faultcode> > <faultstring>Error in the Message Header sent from Server > </faultstring> > <detail> > < rm:rmFault xmlns:rm=”http://schemas.fujitsu.com/rm”> > <rm:faultcode>rm:InvalidMessageHeader</rm:faultcode> > </rm:rmFault> > </detail> > </SOAP:Fault> > </SOAP:Body> > </SOAP:Envelope> > > Best Regards, > > Paolo > > -- > Paolo Romano > > You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]