[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1437) separate subscribing to transaction events
[
https://jira.jboss.org/jira/browse/JBPM-1437?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-1437.
-------------------------------
Resolution: Done
synchronizations are now based on the jta Synchronization class. it is done in a way that
the synchronization class is only used when it is actually needed.
Just realized that this is not totally a user driven choice. Meaning that the PVM engine
itself uses synchronization for its features. So it is not only the user that decides to
use synchronizations and introducing the Synchronization (jta.jar) dependency.
Either we handle this by a wrapper or we state that in the persistent execution mode,
jta.jar is a required dependency.
separate subscribing to transaction events
------------------------------------------
Key: JBPM-1437
URL: https://jira.jboss.org/jira/browse/JBPM-1437
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Critical
currently the Transaction interface extends the Observable interface. this is used to
expose synchronization capabilities.
but the Observable and Listener will move to the internal classes (JBPM-1418). and the
transaction should get its own synchronization listener mechanism.
--
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