|
From: Leif M. <le...@ta...> - 2003-12-01 11:57:00
|
Jacques,
You should be able to download the new jars and place them in the
correct directory.
That should be doable without the Wrapper. (You may have problems with
the IBM JVM?
because it locks the files? This is from memory, so it may be wrong :-/)
Anyway, once you have the new jar files in place, all you need to do
is trigger the
Wrapper to restart the JVM. You could do that using a filter as you
specified or
you could simply call WrapperManager.restart(). I would suggest the
later as it does
not require anything in the wrapper.conf file.
Cheers,
Leif
Jacques Bosch wrote:
>Hi there Leif.
>
>I want to know another thing.
>
>I have a java app that runs unattended and that needs to do a self update to
>the latest version completely independently, without any user intervention.
>The app periodically checks for a new version, and if it finds it, downloads
>the new jar file. But the thing is that the app obviously can't update
>itself.
>I want to know if it is possible to use the wrapper in some way to copy the
>new jar over the old one before starting up the VM again.
>So in that way I would be able to write an "New Update Available..." message
>to the console and catch that with a wrapper filter trigger to restart the
>VM.
>
>Any thoughts or suggestions on how to do this?
>
>Thanx, Jacques
>
>
|