Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Sun, 21 Sep 2014 16:07:34 +0000 (UTC)
From: "Benjamin Graf (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12720869.1402579178000.89628.1411315654068@Atlassian.JIRA>
In-Reply-To: <JIRA.12720869.1402579178000@Atlassian.JIRA>
References: <JIRA.12720869.1402579178000@Atlassian.JIRA>
 <JIRA.12720869.1402579178723@arcas>
Subject: [jira] [Comment Edited] (KARAF-3035) Use aries transaction jdbc /
 jms for pooling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134224#comment-14134224 ] 

Benjamin Graf edited comment on KARAF-3035 at 9/21/14 4:06 PM:
---------------------------------------------------------------

The jdbc feature needs a decision how to handle generic in the future because tranql uses DataSource.getConnection(username, password) which is not implemented by the commons-dbcp BasisDataSource implementation. I would suggest the usage of pax jdbc to close this gap.


was (Author: graben):
The jdbc feature needs a decision how to handle generic in the future because tranql uses DataSource.getConnection(username, password) which is not implemented by the commons-dbcp BasisDataSource implementation. I would suggest to add a similar wrapper into aries jdbc and drop commons-dbcp/pool dependency.

> Use aries transaction jdbc / jms for pooling
> --------------------------------------------
>
>                 Key: KARAF-3035
>                 URL: https://issues.apache.org/jira/browse/KARAF-3035
>             Project: Karaf
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Guillaume Nodet
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)