If it were me, have have the install routine check for the .JAR in use
before doing anything.

Then if it was in use display the jobs using it and tell the user they
must be ended prior to the install. Wouldn't hurt to include a check
to see if the job doing the install is on the list and if so tell the
user to sign off and sign back on without using the app.

In your scenario, what happens once the .jar is installed into a
temporary folder? The user must remember to move it manually later
after figuring out it is safe to do so? Just doesn't seem like a
good idea to me.

Charles

On Tue, Nov 2, 2010 at 5:02 PM, Anna Abt <acosgrove@xxxxxxxxx> wrote:
Our software could be run either way.  That must be the case, the jvm keeps
the lock.  I am writing a procedure for install that will monitor for that
specific case and install in a temporary folder, notifying the user what
happened.  I can't think of any other way around it and I can't control what
clients are doing.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.