I know... the 'compare' has to go deeper... with 3 and 4 NOT storing it to the root level but e.g. using a special node which looks all data up, compares all three and maybe create new tasks (e.g. for the manager) BEFORE storing it at the root level. These kinds of 'decisions' have to be modelled into the process.
When you have threads instead of tasks it is more difficult, but not impossible... still most of the time it has to be in the process. Be it real workflow (e.g. assign to a manager to decide) or bpel like...(have some automatic rule to decide which 'wins') Maybe the engine can help out a little by just giving a warning like 'original value has changed since reading'. This is already possible by using the logging from jBPM, since all updates are stored there. Sounds like some Business Process Isolation Level configuration ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162193#4162193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162193 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
