--- John Sisson <[EMAIL PROTECTED]> wrote:
> Aaron Mulder wrote:
> > I'm not really following your description of how
> this will work, but
> > this is my thought:
> >
> > - We pick a shared library directory
> (var/shared/lib is fine with me)
> > and make that the standard. I don't think shared
Aaron Mulder wrote:
I'm not really following your description of how this will work, but
this is my thought:
- We pick a shared library directory (var/shared/lib is fine with me)
and make that the standard. I don't think shared classes are even
necessary, though I don't object to having a dire
Some additional information in the description below
Joe Bohn wrote:
Sorry, I should have described the function a little better.
There is one shared library gbean that will enhance the classpath with
the jars from any number of shared libraries or shared class
directories.
It updates th
Sorry, I should have described the function a little better.
There is one shared library gbean that will enhance the classpath with
the jars from any number of shared libraries or shared class
directories. The gbean is a child of rmi-naming. An application that
wants to use the shared libra
I'm not really following your description of how this will work, but
this is my thought:
- We pick a shared library directory (var/shared/lib is fine with me)
and make that the standard. I don't think shared classes are even
necessary, though I don't object to having a directory for that too.
Dain added some initial support for shared libraries in 1.1 and (with
the help of David Jencks) I have a configuration and gbean to make the
feature available to applications to use. I'll create a patch for this
today for Geronimo 1.1.
However, I have a question about how "public" we want t
