D
dtharp
We have an application deployed via webstart. The currently deployed
version is 1.0, and I'm currently testing the upgrade process for our
upcoming 1.1 release. The 1.1 version of our app added 3 .jars.
When I click on the jsp which builds the jnlp, webstart correctly comes
up, and starts downloading new jars as expected. All apparently goes
well. In fact, when I start the application, I'm presented with the
interface I recognize from the 1.1 version. So far so good.
Ah... but the login fails right away... the exception indicates a
missing jar file. Looking in webstart's cache, I see that indeed, the
jar is missing. Now for the wierd part: If I remove the app from
webstart, and go through the same sequence (click the jsp)... again the
jars appear to download, and all seems normal. Starting the app this
time results in a normally functioning app. Looking in webstart's cache
: the 3 new jars are there.
Great. I can't believe the solution for this is to have every deployed
PC remove the app from thier webstart. This is going to make for a
tedious upgrade cycle to say the least.
Obviously, something is being cached somewhere... Help!
Thanks in advance.
-D Tharp
version is 1.0, and I'm currently testing the upgrade process for our
upcoming 1.1 release. The 1.1 version of our app added 3 .jars.
When I click on the jsp which builds the jnlp, webstart correctly comes
up, and starts downloading new jars as expected. All apparently goes
well. In fact, when I start the application, I'm presented with the
interface I recognize from the 1.1 version. So far so good.
Ah... but the login fails right away... the exception indicates a
missing jar file. Looking in webstart's cache, I see that indeed, the
jar is missing. Now for the wierd part: If I remove the app from
webstart, and go through the same sequence (click the jsp)... again the
jars appear to download, and all seems normal. Starting the app this
time results in a normally functioning app. Looking in webstart's cache
: the 3 new jars are there.
Great. I can't believe the solution for this is to have every deployed
PC remove the app from thier webstart. This is going to make for a
tedious upgrade cycle to say the least.
Obviously, something is being cached somewhere... Help!
Thanks in advance.
-D Tharp