OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-msg] Error handling issues


David:
 
I have some embedded comments related to Section 4.2.3.3 in the 1.08 draft.
 
Regards,
-Arvola

4.2.3.3    Service and Action Element Values

An ErrorList element can be included in a SOAP Header that is part of a message being sent as a result of processing of an earlier message.  In this case, the values for the Service and Action elements are set by the designer of the Service.

<ac>

We should make it clear that an ErrorList element can be piggybacked on a business response message only if the highestSeverity is not Error. Otherwise, a separate Error message must be used. (This rule derives from section 5.1.4 which states that an ErrorList with Error as highestSeverity cannot be present with a Manifest element.)

</ac>

An ErrorList element can also be included in an SOAP Header that is not being sent as a result of the processing of an earlier message.  In this case, if the highestSeverity is set to Error, the values of the Service and Action elements MUST be set as follows:

      The Service element MUST be set to: uri:www.oasis-open.org/messageService/

      The Action element MUST be set to MessageError.

If the highestSeverity is set to Warning, the Service and Action elements MUST NOT be used.

<ac>

The Service and Action elements are not optional. What should they be set to in this case? Are you suggesting that piggybacking on a response message is mandatory if the highestSeverity is not Error?

It may also be useful to add another subsection parallel to 4.2.3.3 to identify the delivery channel that should be used for sending Error messages. If the incoming message that is in error asks for a synchronous reply, then the Error message should be returned synchronously. Otherwise, the CPA should be consulted to determine the appropriate delivery channel for a standalone Error message. This delivery channel must not specify the use of reliable messaging because Error messages must not be acknowledged.

</ac>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC