The engine will make sure request a is completed before starting request b.
Did I understand this correct? With Singleton Session strategy, one jBPM5 engine can execute one long-running/persistent process at a time? Irrespective of if this ksession has any rule or not?
If that is the case, is this a practical strategy (except for unit testing)?
Kris:
Will version 6.0 support ksession per process instace strategy?