> >>But except for the missing gnujaxp.jar (which I actually locally added in >> the >>Jmol.jar), we also had problems with testing for the availability of >> JAXP... >>which is not, but the exception thrown were not catched... >>InstantiationException and ClassNotFoundException... > > > This is deja vu all over again, but Miguel explained that removing the > XML parser was going to make Jmol.jar smaller.
I did not say tha removing it would make it smaller. I said that *adding* an XML parser would make it 230K *bigger* > The actual distribution of > Jmol.jar V10 is not in fact smaller than all earlier versions. It is not smaller because *no* verson of Jmol 10 *ever* included CML support on anything other than the XML parser which was built into Java 1.4 > Now, > adding gnujaxp.jar > will make it about 230K bigger. and it means some people will have a > customised version > of Jmol.jar into which gnujaxp.jar has been bundled. > > What is more pernicious is that on OS X, gnujaxp.jar appears to come > from the system > Java somewhere, Yes, there is an XML parser included in Java 1.4 ... a product which is approx 2.5 years old. > But I have just had one OS X user report that his system > behaves like Windows, ie gnujaxp.jar > appears to be missing from his system somehow? That is because he is running Java 1.3 ... a product which is approximately 4 years old. And a version on the Mac which is *not* supported by Jmol. > This variability worries me, and makes > me feel that gnujaxp.jar should be included on ALL released versions > of Jmol.jar. ? > finally, if one is developing a Web page, and during this process, the > Jmol.jar is > updated on the server, it can be FIENDISHLY difficult to update the > cached browser version. > Most browsers seem to so persistently cache the .jar archive > that it can be > very difficult to refresh it and hence persuade the browser to download a > new version. My experience is different. It is clearly documented that you must exit all instances of the browser when you change the applet on the server. I have *never* had a problem with .jar files being out of date on the server. I have *never* gone into my browser preferences and pressed 'clear cache'. Close all instances of the browser (like you are supposed to do) and everything will be fine. > does anyone have any good advice on how to reliably clear out cached > versions of .jar files? > At very least, I find I have to quit the browser and restart > it, Yes, because that is what you are supposed to do. > but each browser seems to have a different way of > achieving this. Is there a reliable > formula? Exiting all instances of the browser and restarting should be sufficient. Miguel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
