Re: Need to revise my JNLP file
On Jul 14, 1:35 am, Ramon F Herrera <ra...@conexus.net> wrote:
This is a follow-up question, related to JNLP development.
Why was it necessary to quote the entire original
post in the follow-up question?
It seems that my debugging may be affected by running a version(s)
from the cache. I am not sure if the cached stuff is the remote JNLP
file, the downloaded (hopefully) executable JAR and/or the auxiliary
JARs with libraries and images.
How can I make sure that only the latest and greatest versions are
Well, I'm not so sure about debugging off the site,
but generally during development, I launch a local
version of the app. and override the codebase at
If you are concerned about Jar versions, insert an
Implementation-Version in the manifest of each Jar.
JNLP versions, add a property or argument to the
JNLP file. Log both at runtime.
AFAIU, the JNLP servlet provides ways to get over a
lot of caching problems, but I have not had cause to
use it yet.
If you really need to absolutely guarantee a fresh
install, try temporarily moving the Java cache
location. That will get around both Jar and JNLP
caching (so long as you are not fool enough to try
launching the app. from an existing menu item or