|
From: Leif M. <le...@ta...> - 2003-12-01 13:07:44
|
Jacques,
In that case, you may have to play with class loaders. You will
have a bootstrap
class whose job is to look in a upgrade directory when it first starts.
If there are any new
jars, they are moved into the current jars dir. The bootstrap class
then actually calls the
real main method of your application.
I don't think the jars will be locked until after they are actually
accessed. So as long as
your bootstrap class is in its own stable and independent jar then this
should work. If not
then you will have to have your bootstrap class create a new class
loader, which in turn
builds up a classpath and so on. Classloaders can be a bit of a pain,
so hopefully the first
option will work.
Be sure to post back with the results.
Cheers,
Leif
Jacques Bosch wrote:
>Leif. The app is deployed with the Sun JVM and it also locks the jars. So my
>problem is that I cannot replace the old jar file with the new one while the
>VM is still running.
>
>
|