On Sun, Aug 7, 2011 at 9:33 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Hello all! > > Claus figured out (and I have double checked it), that Camel has no > component which depends on commons-dbcp. I propose to remove the dependency > in the Camel feature file and add a note to the release notes. > > When the user decide to use commons-dbcp (e.g. instead of c3po or the native > pooling capability of the database driver), then he has to add this > dependency to his own feature file (and can choose any version he wants). In > my opinion it's the same as with the database driver which must also be part > of the users feature file. > > What do you think? > > Best, > Christian >
Installing the commons-dbcp in karaf would be as easy as just doing a osgi:install right? I would prefer if Karaf / SMX had some sort of jdbc features you could install and leverage out of the box. A bit similar to what you see in JEE servers for setting up connection pools, and having management and monitoring out of the box. AFAIR there is no such service. And thus people have to rely on commons-dbcp or other connection pooling. But then they have a bit hazzle to monitor and manage that at runtime. If Karaf / SMX had such a jdbc feature then I would be +1 for removing it from the Camel features files. I wonder if any existing users rely on the commons-dbcp and thus in case of an upgrade would hit any trouble? I guess not everyone would read release notes / upgrade guides etc. But just go for it, and then hit an issue with commons-dbcp not present anymore. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
