AnsweredAssumed Answered

explorer transactionality

Question asked by heymjo on Feb 24, 2011
Latest reply on Feb 25, 2011 by heymjo

Since the explorer uses REST to drive all its workflow interactions from the work list, how can one guarantee good transactional behaviour for the case where for example a java service task updates another database schema ? It is possible that the service task runs through fine and commits, but that the subsequent activiti engine database updates (to advance the workflow) fail due to exceptional error conditions e.g tablespace is full, datasource has no free connections …

Is this scenario considered as a known risk in the current architecture ?

For our workflow use cases i would have preferred if the explorer would just use the engine directly with a configured datasource, that would probably make it trivial to have all db interaction during workflow execution enlisted in an XA transaction.