[Wrapper-user] Re-read wrapper.conf on restart?

[Todd K. <tod...@ac...>]

Hi,

=20

I am using Wrapper 3.0.5 and have the following classpath set in
wrapper.conf:

=20

wrapper.java.classpath.1=3D../lib/*.jar

wrapper.java.classpath.2=3D../lib/*.zip

=20

I would like to support upgrade capability in my application whereby new
jars are sent to the application via JMS and written to the applications
lib directory (referenced by the classpath above).  As soon as the new
jars are downloaded, I restart the app using WrapperManager.restart().
Unfortunately, it seems that the wrapper does not rebuild the classpath
on restart, because I get ClassNotFound exceptions for classes
referenced in the new jars after the restart.  A complete shutdown and
restart of the app works fine (but doesn't meet the goal of being fully
automatic!).  These are usually new third-party jars, so they were not
in the classpath before the upgrade.

=20

I even tried programmatically modifying wrapper.conf to explicity add a
reference to the new jar, like this:

=20

wrapper.java.classpath.3=3D../lib/newjar.zip

=20

but it seems that the wrapper doesn't even re-read wrapper.conf on a
restart. =20

=20

Is there any way to force the wrapper to re-read the conf file?  Any
other way to accomplish this?  Any comments/suggestions welcome!

=20

Thanks,

Todd

=20

=20