You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Benjamin Graf (JIRA)" <ji...@apache.org> on 2014/06/02 22:05:01 UTC

[jira] [Reopened] (ARIES-1150) Add support for creating non xa DataSource

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

Benjamin Graf reopened ARIES-1150:
----------------------------------


Just found a very small issue its better to check for XADataSource first since implementation might extend DataSource implementation. (e.g. Derby DB)

> Add support for creating non xa DataSource
> ------------------------------------------
>
>                 Key: ARIES-1150
>                 URL: https://issues.apache.org/jira/browse/ARIES-1150
>             Project: Aries
>          Issue Type: Improvement
>          Components: Transaction
>            Reporter: Benjamin Graf
>            Assignee: Guillaume Nodet
>            Priority: Minor
>              Labels: features
>             Fix For: transaction-jdbc-2.1.0
>
>         Attachments: vcs-diff6821292441619429565.patch
>
>
> Actually you need an XADataSource to get handled by transaction-jdbc. I might be useful to have one abstraction layer to configure either non xa DataSources and XADataSources the same way with the same capabilities (pooling/error handling/...). May be in an generic way by providing specific driver class information. The benefit of that unique approach would be to get all kinds of DataSource configuration the same way on top of the geronimo core libraries. The transaction flag (none/local/xa) might be used for distinction.



--
This message was sent by Atlassian JIRA
(v6.2#6252)