"plalloni" wrote : Ok, we solved it! Glad to hear it! "plalloni" wrote : we didn't see the part of docs where it says that we must persist process definition before its instances. This is a subtle one. The database example in Chapter 3 of the jBPM user guide starts with saving the definition... "plalloni" wrote : we were planning to put some transaction interceptor around those methods (which weren't in place yet) Hibernate (and hence jBPM) can be made aware of managed transactions, in which case the calls to beginTransaction() or commitTransaction() need not be present. You must explicitly demarcate transactions in an unmanaged environment. If you want to move freely between both environments, just leave the demarcations. Hibernate will ignore them in the managed case.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915607#3915607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915607 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
