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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

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


Subject: [ebxml-dev] Fork and Join semantics in BPSS 1.04 ver


Hi,

I was trying to understand the interpretation of fork and join semantics in BPSS.

The 1.04 version of BPSS spec (draft format) explicitly says (pg. 31 line 1186) a fork can exist without a join. Is the reverse true? Can a join exist without a fork?
I can think of a couple of scenarios why a join could exist without fork:

1. A Binary collaboration process graph as shown below (what I have tried to depict is a case where a Join joins two paths from different forks.)
    Here though there is a fork, the join is not a "corresponding join".

    Legend: yellow boxes = forks; purple box = join; green circle = biz transaction activity


 

2. Another case I can think of is a Binary collaboration process graph containing transitions into a join with the join having the parameter waitForAll = false.
    Here the join doesn't need to have any fork.
    Legend: yellow boxes = forks; purple box = join; green circle = biz transaction


 

Could anyone please throw light on these semantics?

Thanks in advance,
Nandini.
 
 
 
 
 
 
 
 
 



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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC