[jira] Resolved: (SYNAPSE-573) Using UserTransaction interfacr instead of TransactionManager interface in tx mediator

["Ruwan Linton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNAPSE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruwan Linton resolved SYNAPSE-573.
----------------------------------

       Resolution: Fixed
    Fix Version/s: NIGHTLY

Fixed on the trunk, thanks for the contribution Rajika

> Using UserTransaction interfacr instead of TransactionManager interface in tx mediator
> --------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-573
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-573
>             Project: Synapse
>          Issue Type: Wish
>          Components: Core
>         Environment: All
>            Reporter: Rajika Kumarasiri
>            Assignee: Ruwan Linton
>             Fix For: NIGHTLY
>
>         Attachments: SYNAPSE-573.patch
>
>
> I am not sure why the TransactionManager interface was used when implementing the tx mediator. But the documentation says when we need to move the tx mangement boundries to application server we need to use TransactionManager interface. 
> How ever using this(TransactionManager) with more that one data sources caused me  resource enlist exception. So I just switched to UserTransaction Interface and then it works fine with more than one datasources. I am attaching the changes as a patch. (If anybody interested I can attach the configuration files used.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org