karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Graf <benjamin.g...@gmx.net>
Subject Re: JDBC Feature
Date Sat, 18 Jan 2014 14:02:39 GMT
Hi JB,

what I'm missing is a link to aries transaction jdbc which is in my 
opinion the better template to provide out of the box. I think it's 
worth thinking about a closer integration of this feature rather than 
doing dbcp stuff for example. Well, of course that is a personally point 
of view if you prefer to go with geronimo stuff providing jee APIs and 
implementations or any other lib out there. :) May be it also worth 
looking to integrate aries transaction jms for the karaf jms enterprise 
feature. (Karaf vs. ServiceMix ?)


On 18.01.2014 10:52, Jean-Baptiste Onofré wrote:
> Hi Benjamin,
> if you take a deeper look, you will see that Karaf JDBC uses Aries 
> (blueprint and transaction).
> Template files uses blueprint. The generic template uses DBCP, the 
> other templates use specific database/JDBC driver capability. But it's 
> only template, you can deploy your own datasource definition.
> The Karaf JDBC module provides what is not in Aries: management of 
> datasource, JDBC service, MBean and shell commands.
> So it's not different, it's a complement.
> Regards
> JB
> On 01/18/2014 09:40 AM, Benjamin Graf wrote:
>> Hi,
>> actually a lot of JDBC stuff has been done for karaf. I'm just wondering
>> why it is done so heterogeneously in different apache projects. Karaf
>> uses blueprint and (not all the time!) dbcp for pooling and creating
>> datasources. Aries uses blueprint as well (:-)) but using
>> geronimo/tranql for pooling and creating. Since aries is part of karaf
>> enterprise, why using yet another enterprise abstraction? By the way. I
>> think aries has done a lot of good work to make working with JDBC quite
>> handy.
>> Just my 0.02€
>> What do you think?
>> Regards
>> Benjamin

View raw message