RE: [ebxml-bp] ebBP 3/15/2005: Comments re: AnyProtocolFailure Update (wd 10)

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

The missing values are at least

 

>     * RequestReceiptFailure

>     * RequestAcceptanceFailure

>     * ResponseReceiptFailure

>     * ResponseAcceptanceFailure

>     * SignalTimeout

>     * ResponseTimeout

 

Also, it was not clear to me how the diagram showed how the values overlapped and what events went with what status values.

 

                       Success

                         //     \\

     ProtocolSuccess   BusinessSuccess

                                  {specific doc or docs received}

 

 

                          Failure

 

                  //                                \\

BusinessFailure                         AnyProtocolFailure

{specific doc or docs received}

                                                 //                   ||                                          \\                                                                            \\

                             ResponseTimeout        SignalTimeout                       [Response|Request] [Receipt|Acceptance] Failure       {GeneralException?}

                          

                             {TTP exceeded}           {TimeToAck/Accept exceeded}                   {ReqAE, ReqRE, RespAE, RespRE}

 

 

The current diagram does indicate a dependency of Protocol Success for either Business Success that was not brought out by the trees I had imagined. So I think different relations (all of which convey useful information, to me at least) are being represented

 

But I think this location in the text would be a good place to add the new information about subtypes. Is ResponseTimeout a kind of ProtocolFailure? (I think so.) Is it a kind of SignalTimeout (I’d guess not.)  Is ResponseTimeout a kind of BusinessFailure? (I think the spec. is saying that only happens when a document is received that has the special business purpose of indicating a business failure (but is not necessarily a NOF). If so, a failure to have a business response sent in time is only a protocol failure in our way of describing things.)

 

 

 

 

 

---

From: Monica J. Martin [mailto:Monica.Martin@Sun.COM]
Sent: Tuesday, March 15, 2005 4:04 PM
To: Jean-Jacques Dubray
Cc: David Webber (XML); Dale Moberg; Steve Capell; ebXML BP; Himagiri.Mukkamala@sybase.com
Subject: Re: [ebxml-bp] ebBP 3/15/2005: Comments re: AnyProtocolFailure Update (wd 10)

 

Jean-Jacques Dubray wrote:

Don't we have this diagram yet? There is a business transaction diagram

detailing all the failures that can happen. Are you looking to enhance

that diagram?

(that figure was in 1.1)

JJ-

mm1: JJ, there are some state transitions that are not represented (See Figure 11 in wd 10) [attached below].