[jbpm-issues] [JBoss JIRA] Created: (JBPM-1457) decide on synchronization exceptions

[Tom Baeyens (JIRA)]

decide on synchronization exceptions
------------------------------------

                 Key: JBPM-1457
                 URL: https://jira.jboss.org/jira/browse/JBPM-1457
             Project: JBoss jBPM
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: PVM
            Reporter: Tom Baeyens
            Priority: Critical


Synchronizations are used for at least 2 purposes:

* executing a transactional exception handler in a separate new transaction after the rollback has occurred
* notifying the job executor when a job is added

more use cases might come later.

Now it turns out that hibernate implemented a different exception handling in the JDBCTransaction then in the JTA spec:

http://forum.hibernate.org/viewtopic.php?p=2392143#2392143

So we can expect different behaviour in standard vs enterprise environments in this respect. We need to decide how we're going to handle this.  One option is to customize the JDBCTransaction and use that.  Another is just document the limitation.  But then we need to know exactly what can go wrong and where.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira