I think it's really important to get rigorous about defining transaction behavior. The default transaction scope across nodes needs to be obvious to the process author. Currently, if I'm not mistaken, the transaction scope is controlled mostly by whether activities are synchronous or not, i.e., by whether a transition is taken within the execute() method of an activity, or a transition is taken because of some external event (e.g., a simple timer node). This is a detail of the implementation of the activity that may not be obvious to the process author. Similarly, the interaction between rollbacks in delegation classes and PVM's process-state persistence needs to be clear. Since Bonita doesn't even allow transactions to span activities, this probably isn't a concern there - it's mostly an issue for JPDL or anything else that tries to address "microflow" requirements. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134577#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...