You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Dain Sundstrom <da...@iq80.com> on 2006/04/05 20:45:14 UTC
Shared Libs
One new feature I'm working on for 1.1 is support for tomcat style
shared libs. This creates a shared class loader visible to all j2ee
applications which contains shared/lib/*.jar and shared/classes/ to
the class loader.
Will this address your issues?
-dain
On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>
> I have a situation where I need to make several web modules
> dependent upon a large number of jars. I'd like to add the jars to
> the Geronimo repo and add the dependencies into the plans for the
> web modules. However, most of the jars don't follow the maven
> naming convention because the names don't include a version (and
> I'd rather not rename all the jars).
>
> I know that there are changes being included in 1.1 to make the
> version in a reference optional. However, I doubt that it is
> possible to reference a jar in the repo that doesn't contain any
> version. Just thought I should ask in case it really is possible.
> I could see where this might be something users would like when
> they have picked up jars from various places which may or may not
> contain a version in the jar name.
>
> If it *is* possible to have a non-versioned jar in the repo ... how
> do we differentiate in geronimo 1.1 between a dependency on a non-
> versioned jar versus a dependency on the latest version of a jar
> (in case both are present).
>
> Thanks for the help,
> Joe
>
> --
> Joe Bohn
> joe.bohn at earthlink.net
>
> "He is no fool who gives what he cannot keep, to gain what he
> cannot lose." -- Jim Elliot
Re: Shared Libs
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Consider this:
I get my Geronimo environment set up perfectly -- security, database,
JMS, dependencies in the repo, etc. I deploy the empty shell of the
application I want to develop (myapp-1.0.ear).
Now I tell the rest of my team: Install Geronimo, go into the console
Import/Export screen, enter the URL for my machine, click the link to
install myapp-1.0.ear.
Everyone who does that gets the empty application, database pool,
security realm, JMS resources, dependencies in the repo, etc. and can
immediately start development on the application. Too bad it doesn't
check out the code for you too! :)
Thanks,
Aaron
On 4/5/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> Aaron,
>
> For the use case of exporting the configuration how do you think folks would use that? At least
> based on my experience with WebSphere and the other AppServers I've often gotten questions from
> people who after using teh big AppServers are torn between the incremental benefit of going to the
> full product and leaving the simplicity of something like Tomcat. I think the shared lib will help
> to bridge that gap for many people. And for those who use it, they probably won't be concerned
> about exporting a configuration.
>
> Aaron Mulder wrote:
> > I'm not so keen on the shared libs, because then we don't know what
> > the dependencies are and it won't be easy to export a configuration
> > with all the necessary metadata. It might be possible to include a
> > flag in the deployment plan saying "enable shared libs" and then if
> > that's set we can refuse to export the configuration or set a special
> > flag saying that the configuration has unknown dependencies. But
> > needing to enable the shared libs would make them a little harder to
> > use. I'm not sure what to think.
> >
> > Thanks,
> > Aaron
> >
> > On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
> >
> >>One new feature I'm working on for 1.1 is support for tomcat style
> >>shared libs. This creates a shared class loader visible to all j2ee
> >>applications which contains shared/lib/*.jar and shared/classes/ to
> >>the class loader.
> >>
> >>Will this address your issues?
> >>
> >>-dain
> >>
> >>On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
> >>
> >>
> >>>I have a situation where I need to make several web modules
> >>>dependent upon a large number of jars. I'd like to add the jars to
> >>>the Geronimo repo and add the dependencies into the plans for the
> >>>web modules. However, most of the jars don't follow the maven
> >>>naming convention because the names don't include a version (and
> >>>I'd rather not rename all the jars).
> >>>
> >>>I know that there are changes being included in 1.1 to make the
> >>>version in a reference optional. However, I doubt that it is
> >>>possible to reference a jar in the repo that doesn't contain any
> >>>version. Just thought I should ask in case it really is possible.
> >>>I could see where this might be something users would like when
> >>>they have picked up jars from various places which may or may not
> >>>contain a version in the jar name.
> >>>
> >>>If it *is* possible to have a non-versioned jar in the repo ... how
> >>>do we differentiate in geronimo 1.1 between a dependency on a non-
> >>>versioned jar versus a dependency on the latest version of a jar
> >>>(in case both are present).
> >>>
> >>>Thanks for the help,
> >>>Joe
> >>>
> >>>--
> >>>Joe Bohn
> >>>joe.bohn at earthlink.net
> >>>
> >>>"He is no fool who gives what he cannot keep, to gain what he
> >>>cannot lose." -- Jim Elliot
> >>
> >>
> >
> >
> >
>
Re: Shared Libs
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Aaron,
For the use case of exporting the configuration how do you think folks would use that? At least
based on my experience with WebSphere and the other AppServers I've often gotten questions from
people who after using teh big AppServers are torn between the incremental benefit of going to the
full product and leaving the simplicity of something like Tomcat. I think the shared lib will help
to bridge that gap for many people. And for those who use it, they probably won't be concerned
about exporting a configuration.
Aaron Mulder wrote:
> I'm not so keen on the shared libs, because then we don't know what
> the dependencies are and it won't be easy to export a configuration
> with all the necessary metadata. It might be possible to include a
> flag in the deployment plan saying "enable shared libs" and then if
> that's set we can refuse to export the configuration or set a special
> flag saying that the configuration has unknown dependencies. But
> needing to enable the shared libs would make them a little harder to
> use. I'm not sure what to think.
>
> Thanks,
> Aaron
>
> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>
>>One new feature I'm working on for 1.1 is support for tomcat style
>>shared libs. This creates a shared class loader visible to all j2ee
>>applications which contains shared/lib/*.jar and shared/classes/ to
>>the class loader.
>>
>>Will this address your issues?
>>
>>-dain
>>
>>On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>>
>>
>>>I have a situation where I need to make several web modules
>>>dependent upon a large number of jars. I'd like to add the jars to
>>>the Geronimo repo and add the dependencies into the plans for the
>>>web modules. However, most of the jars don't follow the maven
>>>naming convention because the names don't include a version (and
>>>I'd rather not rename all the jars).
>>>
>>>I know that there are changes being included in 1.1 to make the
>>>version in a reference optional. However, I doubt that it is
>>>possible to reference a jar in the repo that doesn't contain any
>>>version. Just thought I should ask in case it really is possible.
>>>I could see where this might be something users would like when
>>>they have picked up jars from various places which may or may not
>>>contain a version in the jar name.
>>>
>>>If it *is* possible to have a non-versioned jar in the repo ... how
>>>do we differentiate in geronimo 1.1 between a dependency on a non-
>>>versioned jar versus a dependency on the latest version of a jar
>>>(in case both are present).
>>>
>>>Thanks for the help,
>>>Joe
>>>
>>>--
>>>Joe Bohn
>>>joe.bohn at earthlink.net
>>>
>>>"He is no fool who gives what he cannot keep, to gain what he
>>>cannot lose." -- Jim Elliot
>>
>>
>
>
>
Re: Shared Libs
Posted by Dain Sundstrom <da...@iq80.com>.
I'm not keen on the shared libs concept either, but people are
familar with the feature from Tomcat.
I think we would get tons of emails from confused users if this
feature is not on by default. When it comes to exporting
configurations, we could warn users that the application can see
shared libraries and they will have to install they by hand on the
target server. Alternatively, we could allow the user to select the
shared libs to include in the export, and then we we do an import ask
the user if they want the jars added to the shared libs, or kept
private.
I think we should start with the first option as it is the easiest
and hopefully someone will implement the second.
-dain
On Apr 5, 2006, at 12:05 PM, Aaron Mulder wrote:
> I'm not so keen on the shared libs, because then we don't know what
> the dependencies are and it won't be easy to export a configuration
> with all the necessary metadata. It might be possible to include a
> flag in the deployment plan saying "enable shared libs" and then if
> that's set we can refuse to export the configuration or set a special
> flag saying that the configuration has unknown dependencies. But
> needing to enable the shared libs would make them a little harder to
> use. I'm not sure what to think.
>
> Thanks,
> Aaron
>
> On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
>> One new feature I'm working on for 1.1 is support for tomcat style
>> shared libs. This creates a shared class loader visible to all j2ee
>> applications which contains shared/lib/*.jar and shared/classes/ to
>> the class loader.
>>
>> Will this address your issues?
>>
>> -dain
>>
>> On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>>
>>>
>>> I have a situation where I need to make several web modules
>>> dependent upon a large number of jars. I'd like to add the jars to
>>> the Geronimo repo and add the dependencies into the plans for the
>>> web modules. However, most of the jars don't follow the maven
>>> naming convention because the names don't include a version (and
>>> I'd rather not rename all the jars).
>>>
>>> I know that there are changes being included in 1.1 to make the
>>> version in a reference optional. However, I doubt that it is
>>> possible to reference a jar in the repo that doesn't contain any
>>> version. Just thought I should ask in case it really is possible.
>>> I could see where this might be something users would like when
>>> they have picked up jars from various places which may or may not
>>> contain a version in the jar name.
>>>
>>> If it *is* possible to have a non-versioned jar in the repo ... how
>>> do we differentiate in geronimo 1.1 between a dependency on a non-
>>> versioned jar versus a dependency on the latest version of a jar
>>> (in case both are present).
>>>
>>> Thanks for the help,
>>> Joe
>>>
>>> --
>>> Joe Bohn
>>> joe.bohn at earthlink.net
>>>
>>> "He is no fool who gives what he cannot keep, to gain what he
>>> cannot lose." -- Jim Elliot
>>
>>
Re: Shared Libs
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I'm not so keen on the shared libs, because then we don't know what
the dependencies are and it won't be easy to export a configuration
with all the necessary metadata. It might be possible to include a
flag in the deployment plan saying "enable shared libs" and then if
that's set we can refuse to export the configuration or set a special
flag saying that the configuration has unknown dependencies. But
needing to enable the shared libs would make them a little harder to
use. I'm not sure what to think.
Thanks,
Aaron
On 4/5/06, Dain Sundstrom <da...@iq80.com> wrote:
> One new feature I'm working on for 1.1 is support for tomcat style
> shared libs. This creates a shared class loader visible to all j2ee
> applications which contains shared/lib/*.jar and shared/classes/ to
> the class loader.
>
> Will this address your issues?
>
> -dain
>
> On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>
> >
> > I have a situation where I need to make several web modules
> > dependent upon a large number of jars. I'd like to add the jars to
> > the Geronimo repo and add the dependencies into the plans for the
> > web modules. However, most of the jars don't follow the maven
> > naming convention because the names don't include a version (and
> > I'd rather not rename all the jars).
> >
> > I know that there are changes being included in 1.1 to make the
> > version in a reference optional. However, I doubt that it is
> > possible to reference a jar in the repo that doesn't contain any
> > version. Just thought I should ask in case it really is possible.
> > I could see where this might be something users would like when
> > they have picked up jars from various places which may or may not
> > contain a version in the jar name.
> >
> > If it *is* possible to have a non-versioned jar in the repo ... how
> > do we differentiate in geronimo 1.1 between a dependency on a non-
> > versioned jar versus a dependency on the latest version of a jar
> > (in case both are present).
> >
> > Thanks for the help,
> > Joe
> >
> > --
> > Joe Bohn
> > joe.bohn at earthlink.net
> >
> > "He is no fool who gives what he cannot keep, to gain what he
> > cannot lose." -- Jim Elliot
>
>
Re: Shared Libs
Posted by Dain Sundstrom <da...@iq80.com>.
On Apr 5, 2006, at 12:55 PM, Joe Bohn wrote:
> I think the shared libraries may solve this issue for a lot of people.
>
> Do you have some more thoughts on how this capability may be made
> available to users? Looking at what was checked in already it
> seems that the user would have to create an array of the libDirs in
> code via some home-grown mechanism and then invoke your class to
> update the classpath. Do you already have plans for an easier way
> to expose this to the users (perhaps via some server configuration
> or some new elements on the deployment plans to add new shared
> libraries)?
The code is not finished :) Is that is will work exactly like
tomcat. The code I checked is a GBean service that will be in a
standard configuration installed into the server. As we deploy j2ee
applications they why have a dependency on this configuration. When
the gbean in this configuration is started it will add the classes
and libraries to the class loader. This will happen automatically
without any user interaction.
-dain
Re: Shared Libs
Posted by Joe Bohn <jo...@earthlink.net>.
I think the shared libraries may solve this issue for a lot of people.
Do you have some more thoughts on how this capability may be made
available to users? Looking at what was checked in already it seems
that the user would have to create an array of the libDirs in code via
some home-grown mechanism and then invoke your class to update the
classpath. Do you already have plans for an easier way to expose this
to the users (perhaps via some server configuration or some new elements
on the deployment plans to add new shared libraries)?
Joe
Dain Sundstrom wrote:
> One new feature I'm working on for 1.1 is support for tomcat style
> shared libs. This creates a shared class loader visible to all j2ee
> applications which contains shared/lib/*.jar and shared/classes/ to the
> class loader.
>
> Will this address your issues?
>
> -dain
>
> On Apr 4, 2006, at 7:35 PM, Joe Bohn wrote:
>
>>
>> I have a situation where I need to make several web modules dependent
>> upon a large number of jars. I'd like to add the jars to the
>> Geronimo repo and add the dependencies into the plans for the web
>> modules. However, most of the jars don't follow the maven naming
>> convention because the names don't include a version (and I'd rather
>> not rename all the jars).
>>
>> I know that there are changes being included in 1.1 to make the
>> version in a reference optional. However, I doubt that it is
>> possible to reference a jar in the repo that doesn't contain any
>> version. Just thought I should ask in case it really is possible. I
>> could see where this might be something users would like when they
>> have picked up jars from various places which may or may not contain
>> a version in the jar name.
>>
>> If it *is* possible to have a non-versioned jar in the repo ... how
>> do we differentiate in geronimo 1.1 between a dependency on a non-
>> versioned jar versus a dependency on the latest version of a jar (in
>> case both are present).
>>
>> Thanks for the help,
>> Joe
>>
>> --
>> Joe Bohn
>> joe.bohn at earthlink.net
>>
>> "He is no fool who gives what he cannot keep, to gain what he cannot
>> lose." -- Jim Elliot
>
>
>
>
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot