[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Isolated scope semantics
Hello, I want to clarify the semantics of the Isolated Scope as defined in "Web Services Business Process Execution Language Version 2.0" specification. Let's define a use case as a process with two concurrent isolated scopes that work on a shared set of variables. What is the correct semantics of such process? a) 2 isolated scopes are seen as database serialization transactions. Once you enter each scope you work with the snapshot of variable values you observed. So commits in one scope will be not seen in the second scope; b) Within one (or) both scopes all the activities are done sequentially (no parallelism allowed); c) Not depending on which order you will execute activities from one (or both) scope(s) the end results on variables will be the same ??!! d) Another one. I ask because what I read and what I discuss with people varies. I am particularly interested in isolated scopes application for modeling interleaved parallel routing workflow pattern and it's relation to the fact that isolated scope might contain control flow. Best regards, Artem
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]