Re: [ebxml-iic] Use cases for concurrent test cases

["Monica J. Martin" <Monica.Martin@Sun.COM>]

> --------------------------------------
> Concurrency Use Case #2: workflow split
> --------------------------------------
> Test Case:
> - send M1
> (---> this will trigger two concurrent subprocesses 2 and 3 on the 
> remote side,
> which will send back two threads of messages: M2a + M2b for subprocess 
> 2, and M3 for
> subprocess 3. There is no order between subprocesses 2 and 3 )
> - split {(receive M2a; verify M2a; receive M2b; verify M2b)(receive 
> M3; verify M3)}
> (---> then when M2a , M2b and M3 have been verified, one last message 
> M4 is expected)
> - receive message M4
> - verify M4
>
mm1: Jacques, on this one, you could have multiple starts (in BPSS 
context).  With an XOR fork-join, only the first is valid and the others 
are disabled. Then again, there could be multiple outgoing transitions 
from a Business Activity when a fork or decision applies.  I think the 
case if that you have multiple starts, where all but one are disabled 
(and verified they are) and the appropriate one continues.  Perhaps this 
is a BPSS case rather than a general one for concurrency. Sorry for 
delay in responding - on vacation. :-)