karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: JDBC Feature
Date Sat, 18 Jan 2014 14:06:53 GMT
Hi Benjamin,

I'm not sure to follow you.

Did you really take a look in the Karaf JDBC or JMS feature. It's mostly 
commands and MBean (not really any runtime providing). We completely 
leverage Aries Transaction for instance.
It's the same for JNDI: we complete Aries JNDI (which doesn't provide 
any initial context) with a very simple XBean naming context.

I'm not sure to see your point. Maybe you think that Karaf JDBC or JMS 
is more than that you think it is actually ;)


On 01/18/2014 03:02 PM, Benjamin Graf wrote:
> 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 ?)
> Regards
> Benjamin
> 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

Jean-Baptiste Onofré
Talend - http://www.talend.com

View raw message