[Fwd: Re: help 4 optional transaction]

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

See question from Cristiano Novelli. If any team members have inputs to 
my response, please add. I see no specification changes at this time.

>> Novelli 17 May 2005: Hi Monica,
>> I want to describe a business process with ebBP... but i don't know 
>> to define optional transactions into a complex situation
>>
>> The situation is the sequent:
>> ------
>> 1. CommercialTransaction A [required]
>> 2. CommercialTransaction B [required]
>>
>> 3. CommercialTransaction C [optional]
>> 4. CommercialTransaction D [optional]
>> 5. RequestResponse E [optional]
>>
>> 6. CommercialTransaction F [required]
>> ------
>> - the order of 3,4,5 is not fixed
>> - 3,4,5 can happen 0 or more
>
> mm1: This could be handled by fork-join. We discussed and the 
> technical specification references (See Section 3.4.11.1 and the 
> discussion of transitions, fork and join) [1].
>
>> example:
>> - It happen 1,2,6
>> - It happen 1,2, 5,4,5,3,5,5, 6
>> - It happen 1,2, 4,5,3, 6
>> - ecc.
>
> mm1: Remember that the choreography is there to help you handle the 
> possible interactions that could occur. They should be modeled to show 
> those potential paths.
>
>> (a "decision" element is inadequate, if fork/join is enough... how 
>> can I use them?).
>
> mm1: See above [1]. I ask Dale, John, Hima and JJ to add if they have 
> more suggestions.
>
>> I'm sorry... I have some solutions but I fear to obtained a twisted 
>> ebBP...
>> Thanks for your support
>> Regards (Ciao)
>