[Jalview-discuss] Web start failing if caching turned off
fred.ludlow at gmail.com
Wed Jan 11 09:39:26 GMT 2012
On 10 January 2012 15:47, Jim Procter <jprocter at compbio.dundee.ac.uk> wrote:
> Could you try to launch jalview again, after first clearing/uninstalling
> it from the web start cache ? (Right click on the corresponding entry in
> the list of java web start apps that are shown when you run 'javaws
> -viewer' from the run dialog box). This should delete any old files that
> are still hanging around.
I've cleared the cache, unfortunately this doesn't fix it, but see below
> Has anyone else encountered / solved this problem? I saw there was a
>> related issue in the FAQ section of the website, but that's to do with
>> having an up to date jnlp file (I'm using the current one from the website,
>> so I don't think that's the issue here).
> Web start is a remarkably fragile mechanism - if anyone can tell us what's
> going on here I'd also appreciate it!!
I tried it on another machine, with Java 1.6.0_15 / Win XP, and it worked
both with and without caching enabled. I then upgraded that machine to the
latest version (1.6.0_30) and I have the same behaviour (works with caching
turned on, fails with it turned off).
The best I could come up with on the web is this link:
The suggestion is that if any referenced jar file's manifest file contains
an entry for a directory it will cause problems when caching is turned off.
castor-1.1-cycle-xml.jar does have entries like:
So maybe removing those from the manifest file would fix it, though I'm not
sure if that would also break something...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jalview-discuss