Re: [ebxml-cppa] Re: [ebxml-msg] Comments on your Comments

[Arvola Chan <arvola@tibco.com>]

Marty:

Lines 1426 and 1427 in the 1.07 version of the spec (with
change bars turned on) state:

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

These values are to be used when an Error message is
sent on its own. Therefore, it is possible to have an Override
element in the CPA to designate the delivery channel to be
used for such messages.

Regards,
-Arvola

-----Original Message-----
From: Martin W Sachs <mwsachs@us.ibm.com>
To: Arvola Chan <arvola@tibco.com>
Cc: David Fischer <david@drummondgroup.com>; ebXML Msg
<ebxml-msg@lists.oasis-open.org>; ebxml-cppa@lists.oasis-open.org
<ebxml-cppa@lists.oasis-open.org>
Date: Tuesday, November 06, 2001 8:26 PM
Subject: [ebxml-cppa] Re: [ebxml-msg] Comments on your Comments


>
>Arvola,
>
>At the moment, the CPPA specification does not provide a means of
>designating delivery channels specifically for error messages. Delivery
>channels can only be designated per action or for the entire set of
>actions.  You are proposing a new issue for the CPPA-MSG interlock list.
>
>Regards,
>Marty
>
>***************************************************************************
**********
>
>Martin W. Sachs
>IBM T. J. Watson Research Center
>P. O. B. 704
>Yorktown Hts, NY 10598
>914-784-7287;  IBM tie line 863-7287
>Notes address:  Martin W Sachs/Watson/IBM
>Internet address:  mwsachs @ us.ibm.com
>***************************************************************************
**********
>
>
>
>Arvola Chan <arvola@tibco.com> on 11/06/2001 08:19:41 PM
>
>To:    David Fischer <david@drummondgroup.com>
>cc:    ebXML Msg <ebxml-msg@lists.oasis-open.org>,
>       ebxml-cppa@lists.oasis-open.org
>Subject:    Re: [ebxml-msg] Comments on your Comments
>
>
>
>David:
>
>I have no problem with stipulating that Errors are never sent
>reliably. We just have to make it clear in the 1.1 spec.
>
>The CPP/A spec should indicate that any delivery channel
>designated for carrying Error messages (i.e., for the action
>MessageError) must not specify the use of Reliable Messaging.
>
>Regards,
>-Arvola
>
>-----Original Message-----
>From: David Fischer <david@drummondgroup.com>
>To: Arvola Chan <arvola@tibco.com>
>Cc: ebXML Msg <ebxml-msg@lists.oasis-open.org>
>Date: Tuesday, November 06, 2001 7:19 AM
>Subject: [ebxml-msg] Comments on your Comments
>
>
>Arvola,
>
>One of your comments was on the restriction about not having Acks on
>Errors.
>We
>can have Acks on Errors if we stipulate no Errors on Acks.  If we want
>Errors on
>Acks then we must stipulate no Acks on Errors.  If we have both, then we
>have
>the potential for endless loops.
>
>I question the need for Errors to be sent reliably.  I see some significant
>benefit for having Errors returned on bad Acks.
>
>Regards,
>
>David Fischer
>Drummond Group.
>
>
>----------------------------------------------------------------
>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>
>
>
>
>
>----------------------------------------------------------------
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.oasis-open.org/ob/adm.pl>