Hi Guillaume, I am living dangerously by placing my stand-alone apps's jars under lib directory since karaf is currently pushing those jars into osgi framework classloader?
Thanks -Dan On Mon, May 13, 2013 at 10:55 AM, Guillaume Nodet <[email protected]> wrote: > 2013/5/13 Dan Tran <[email protected]> > > > For my case, my distribution consists of Karaf container + our bunbles, > + a > > bunch of stand alone apps with bootstrap/startup script generated by > > appassembler-maven-plugin[1]. > > > > The standalone apps ( command line utilities, swing app, etc ) have its > > jars placed under lib directory where the startup/boostrap script will > use > > to construct the extract classpath. > > > > Now, base on Guillaume Nodet comments, I have to think hard about my > > approach, since karaf indirectly load all the jars under lib directory to > > its class loader. The question here, which class loader are we talking > > about here ( system? ) and which component under karaf would care about > > this hidden feature? > > > > The only change I suggested is to slightly alter the shell script to add > lib/system/*.jar to the classpath. > That keeps all existing installation unchanged and allow more control for > the jdbc driver use case. > We need to correctly document the classloading mechanism, but it's a > minimal change which imho cleanly support the needed use case. > > > > > > Thanks > > > > -D > > > > > > > > [1] > > > > > http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/assemble-mojo.html > > > > > > On Mon, May 13, 2013 at 7:40 AM, Heath Kesler <[email protected]> > > wrote: > > > > > +1 > > > > > > Will revert to karaf prefix in the lib and add a sub directory for any > > > required external jar without karat prefix. > > > > > > On May 12, 2013, at 11:53 PM, Dan Tran <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > I have addressed my concerns on this enhancement, and would like to > > hear > > > > more from dev group. > > > > > > > > Big Thanks > > > > > > > > -Dan > > > > > > > > >
