@rocade
Maybe it is better to realise this *outside* jBPM. It is good practice to store a little info as needed in the engine. Have a domain model outside jBPM and relate the data of a belonging to a processinstance to the processinstance by using the (business)key. This is a field on the processinstance.
That way, you can do locking or detecting changes (hibernate versioning!!) outside jBPM. I think that would be a better solution
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163796#4163796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163796
anonymous wrote : jBPM swallows the StaleObjectStateException causing the calling code not to notice that the operation failed. Afaik, that can be configured in jBPM 3.2.3. Please have a look in the docs
@Chessplayer....
I meant to start a new discussion on this 'lost updates' thing (detecting it, throwing errors, leaving as is...). The discussion was held years ago, so reviving is it is hard (old sourceforge forum). I'll draw something up in the weekend to start it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163794#4163794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163794