Douglas If I understood your proposal, it looks like you are investigating a "pattern" or "best practice" to handle exceptions in SCA components. Do you envision any requirements on the SCA Runtime to support this ?
On Sun, Feb 15, 2009 at 8:25 AM, Simon Laws <simonsl...@googlemail.com> wrote: > Hi Douglas > > Interesting post. Look forward to seeing what you come up with. Re. > > "Maybe the travel agency sample, given above, is too simple to justify the > use of such complex (and maybe expensive) mechanisms" > > Maybe it's not simple enough in the very first instance? In the travel agent > sample you have 2 concurrent business processes executing where each process > takes the form: > > Book > Pay > > What would be lost to your scenario if you considered Book and Pay an atomic > operation which leaves you with four combinations; > > success > hotels fails (either flight has or hasn't run) > flight fails (either hotel has or hasn't run) > concurrent exception > > Just a thought. > > Regards > > Simon > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
