Issue - 2 - Reopen the discussion

["Trickovic, Ivana" <ivana.trickovic@sap.com>]

Here is a list of requirements for sub-processes. Sub-processes:
(1) Should/could be understood as outsourced pieces of BPEL codes that can be reused within a process or across multiple processes
(2) Can be defined locally within a single bpel process and reused only within that process, or defined as a top-level bpel process and reused across multiple bpel processes
(3) Are executed in the context in which they are defined 
(4) Must have input/output parameters in order to "pass" data between calling processes and sub-processes; the data is passed by value
(5) Must have definition consistent with bpel scopes/processes
(6) Are tightly coupled with calling processes. That means:
	(6.1) If calling process is terminated the sub-process must be terminated as well (at least in case of synchronous call)
	(6.2) If sub-process fails and cannot recover from the failure, the fault must be propagated to the calling process
	(6.3) Calling process should be able to call the compensation activity of the sub-process 

One aspect has been mentioned in our previous discussion as well: using sub-processes in expressions/conditions. I would definitely exclude this aspect.

It would be worth agreeing on the above-mentioned set of requirements first. 

Regards,

Ivana