RE: [wsbpel] Topics for the "Review input from TC members" session of the F2FSome

["Edwin Khodabakchian" <edwink@collaxa.com>]

> 
> The case I am thinking of is something along the lines of a 
> loan approval process where the loan parameters are submitted 
> and the loan is either approved or denied. To me this is a 
> synchronous request/response interaction; even though the 
> approval process may take weeks, I would like to model such a 
> process without asynchronous callbacks. This is particularly 
> handy when nesting processes (i.e. when the loan approval 
> process is a sub-process of a loan origination process), 
> reducing considerably the complexity of the nesting processes. 
> 

Physically you still need to define asynchronous callback (partnerLinkType,
correlation, callback location). Logically you are also better off exposing
the asynchronous ( invoke/receive ) nature of the interaction to the process
designer because you most likely will need to handle time-outs, status
checks, etc...

I am not sure to understand how having invoke/receive instead of a single
invoke increases the complexity of nesting processes. Could you please
clarify?

Thanks,

Edwin