You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2018/07/24 22:18:00 UTC
[jira] [Resolved] (DBCP-514) Allow DBCP to register with a
TransactionSynchronizationRegistry for XA cases
[ https://issues.apache.org/jira/browse/DBCP-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory resolved DBCP-514.
-------------------------------
Resolution: Fixed
Assignee: Gary Gregory
Fix Version/s: 2.6.0
[~tomjenkinson]:
Thank you for your patch.
I applied a modified patch that does not break binary compatibility, adds @since tags, and missing Javadocs.
I also bumped up the version from {{2.5.1-SNAPSHOT}} to {{2.6.0-SNAPSHOT}} since this patch adds new public APIs.
Please verify and close this issue and the PR if all is well.
Gary
> Allow DBCP to register with a TransactionSynchronizationRegistry for XA cases
> -----------------------------------------------------------------------------
>
> Key: DBCP-514
> URL: https://issues.apache.org/jira/browse/DBCP-514
> Project: Commons DBCP
> Issue Type: Improvement
> Reporter: Tom Jenkinson
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 2.6.0
>
>
> In some scenarios it is possible that there may be other synchronizations that need to register with a transaction manager and there may be a requirement for some ordering to be imposed.
> JTA supports this by providing the ability to register interposed synchronizations with special orderering requirements.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)