The Java EE way of doing it is to use "Installed Optional Packages"
facility of a Java EE platform. Not many servers (that includes
GlassFish as well) implement it as the way it should be. Hence you can't
reliably use it at the moment.
Instead, try using the GlassFish proprietary --library option. You can
specify library jar names during deployment of applications and they
will be used by those applications only. Refer to following places:
https://glassfish.dev.java.net/nonav/javaee5/docs/DG/beade.html#gatej
http://blogs.sun.com/sivakumart/entry/classloaders_in_glassfish_an_attempt
Thanks,
Sahoo
rdblaha1 wrote:
> We have a basic set of jar files we have used for years with utilities (in
> some files they are customer specific). We wish to incorporate access to
> these for each application deployed. Some applications will require more
> than others or some will require access to customer specific jars. Because
> of this we cannot use the shared library concept (if that is indeed what the
> Shared Library is for).
>
> I have deployed an application requiring access to one of our jar libraries.
> When I deployed it or when I launch it I find no place to associate these
> libraries to the deployed application. How do I do this?
>
>
>