Re: [ebxml-iic] minutes, next call Monday 23, and more

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

> Durand: 2. "Exclusive threads":
> How can we implement a test case that will have to run one thread
> out of  two or more possible threads, not knowing which one in advance,
> and must "fail" if more than one have actually been completed / run?
> (this is the meaning of BPSS fork "XOR" I think)
> Do we only need this?
> Here is a (not so good) example: a test case that will send a Purchase 
> Order to the remote party,
> and expect either one of two responses "accept" or "reject", and with 
> a specific
> sequence of exchanges for each response type. We want to fail in case 
> we get both responses.
> One way to implement this, on the Test Driver side, is to run:
> step1: PutMessage()
> step 2:  split (A, R) (each thread A and R will do a GetMessage 
> filtering resp. on "accept" and "reject")
> step 3 orJoin (A, R)
> (but how can we express that in case we get there via A, we  don't 
> even want R to gets its message or
> else we fail?)
> Note that we can also implement this case with :
> step1: PutMessage()
> step 2:  GetMessage() , if ("accept") then thread A else thread R end;
> step 3: ...
> Although in this second script additional unwanted messages would not 
> be detected (in case we get both  "accept" and "reject") as the 1st 
> message received would decide where to go.
>
> One way to implement this "XOR" is , in each thread A and R, start an 
> exception thread that would "fail" if the "other"
> message is received. Any way to do that more simply?
>
mm1: Jacques, in BPSS, if you have the XOR, if one thread starts, the 
others are disabled. However, the question remains if it is the one 
expected. Perhaps you should put together a summary with this example so 
I can query ebBP team. Thanks.