adventure of stale jars
Hello brethren,
I am using webstart for deploying/updating my swing desktop client,
It is a simple JNLP set up where JNLP picks up the application jar and dependent jars from the same directory where it resides,
Now I made some changes to my application code and deployed (through FTP)it on the weblogic HTTPserver,
cleared my cache from JWS home on local machine,
But to my surprise JNLP was picking the old application jar(2.1.0),
hmmmm I then tried to change the version(2.2.0) so to make it less confusing for the WS but no it still persists on picking the old version jar ,
then I thought may be stale jars are there in HTTP server So I cleansed that as well,
cleaned local cache and deployed new version again but WS is stubborn as ever,
Am I pointing to a different URL where some stale JNLP with its stale jar side kicks ruining my day,
OK I removed the jnlp from server then tried running client of course after all the long and tedious cleansing procedure but this time I got an error because I have deleted the JNLP
so at least I know that I am pointing to the right location (the folder where my jars and jnlp are on http server) through URL,
but If I am pointing to the right place
I am having only the latest jar in server with jnlp pointing to that jar only,
with my desktop cache cleaned what can cause the problem ?
why stale jars are still being downloaded even when I am not pointing that version through JNLP.
Then I googled abit and found this site http://lopica.sourceforge.net/faq.html
<property name="javaws.debug.0" value="+TraceSecurity"/>
<property name="javaws.debug.1" value="+TraceCache"/>
<property name="javaws.debug.2" value="+TraceDiskCache"/>
<property name="javaws.debug.3" value="+TraceDownload"/>
<property name="javaws.debug.4" value="+TraceXMLParsing"/>
And then I realized
Found in cache: DisckCacheEntry
.javaws\cache\http\D<URL>\P80\DM<folder where jars are>\RM<stale.jar>;null
Now what that means ?
Please help
