[jboss-jira] [JBoss JIRA] Updated: (JBRULES-2322) Add Support for TransactionSynchronizationRegistry as an option for JTA Transaction Synchronization
Mark Proctor (JIRA)
jira-events at lists.jboss.org
Sat Apr 3 23:28:38 EDT 2010
[ https://jira.jboss.org/jira/browse/JBRULES-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Proctor updated JBRULES-2322:
----------------------------------
Fix Version/s: 5.1.0.M2
Assignee: Kris Verlaenen (was: Mark Proctor)
> Add Support for TransactionSynchronizationRegistry as an option for JTA Transaction Synchronization
> ---------------------------------------------------------------------------------------------------
>
> Key: JBRULES-2322
> URL: https://jira.jboss.org/jira/browse/JBRULES-2322
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: drools-core (flow)
> Affects Versions: 5.1.0.M1
> Reporter: Michael Youngstrom
> Assignee: Kris Verlaenen
> Fix For: 5.1.0.M2
>
>
> In order to use user managed transactions DroolsFlow requires an instance of TransactionManager. An instance of TransactionManager cannot be provide for environments such as Websphere. However, it appears that DroolsFlow only uses the TransactionManager to register some transaction synchronizations. Websphere 7 does support JTA 1.1's TransactionSynchronizationRegistry interface. it would be nice if DroolsFlow were enhanced to support optionally specifying the TransactionSynchronizationRegistry instead of a TransactionManager to better support JTA implementations like Websphere's that doesn't publicly provide a TransactionManager implementation.
--
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
More information about the jboss-jira
mailing list