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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: Propagation of failure information in a multiparty


Hi everyone
 
I guess the following question is answered already.
 
A multiparty collaboration between A, B, and C with the following timely order of Business Transaction Activities:
 
1. BusinessTransactionActivity from A to B
2. BusinessTransactionActivity from B to C
3. BusinessTransactionActivity from B to A
4. BusinessTransactionActivity from A to B
5. BusinessTransactionActivity from B to C
6. BusinessTransactionActivity from B to A
 
So lets say there is a failure in the 3rd BusinessTransactionActivit. This failure is happening with between party A and B so both parties are aware of the failure.
 
This also means that party B must inform party C about the failure.
 
It seems obvious that this is happening.
 
It shall not be the case that party C does not get informed about any failures of a business process that party C is involved and that party C has to wait for a timer to expire.
 
On the other hand if the business process failure happens in Business Transaction Activity 1 then the business process has not even started between B and C and hence ... B does not need to inform about a business process failure to C as C is not even aware that there has been a business process started.
 
Regards
 
Sacha


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