There are a few ways you can install system-wide libraries:
1) Put them in ${domain-dir}/ext. It requires server restart. There is a
limitation that libraries installed in that location can't depend on
Java EE APIs.
2) Put them in ${domain-dir}/lib. This also requires server restart. The
afore-mentioned restriction does not apply here.
3) Use --libraries option while deploying.
In all the options above, there will be a single copy of the library
shared by all apps. Please refer to GlassFish documentation for more
details.
Coming to your second requirement, no, GlassFish does not yet support
runtime updation of libraries. It's coming in V3.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> I too am having the same issue. I have several service classes/jJARs that are shared among multiple disparate WARs. I don't want to make them remote EJB services since that will be a performance penalty - and I don't want to bundle copies of them into each WAR (there are many WARs). I'd like to make the classes/JARs available at the server level WITHOUT using the system or server classpath. Basically, I'd like the ability to deploy an UPDATED set of the services dynamically and have those changes be visible to the WARs. Is that possible? I tried registering my JARs as a JBI component (I'm a bit new to that) but the WARs could not see the classes.
> [Message sent by forum member 'csiemback' (csiemback)]
>
> http://forums.java.net/jive/thread.jspa?messageID=267284
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>