From: Egon W. <e.w...@sc...> - 2005-02-16 21:28:11
|
On Wednesday 16 February 2005 09:05 pm, Miguel wrote: > > I have tracked it down to the following. If eg a .mol or .xyz file is > > loaded, it has no problems on either > > > Mac or Windows. But if a CML file is loaded (as here), > > on Windows one appears to get > > the following errors. Is this a SAX parser error? > > I thought this was built into Jmol (V 10.0?). > > Perhaps this is not the case? > > Remind me of how this additional jar would be loaded? > > There is no XML parser built into the Java 1.1 libraries. Therefore, in > order to support CML on IE Windows you must provide an additional .jar > file: gnujaxp.jar > > You are writing your own [applet] tags. One of the attributes is > archive='JmolApplet.jar' > > change this to be > archive='JmolApplet.jar,gnujaxp.jar' Miguel, Hens is using CML now for partial charges and bond orders (the latter are not possible in XYZ), and we had a class room with no Sun JVM, so only MSFT JVM... 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... You might recall this problem in the LoggingTool about 1.5 years ago... I tried to fix it, but did not succeed in the 20-ish minutes I had... And did not have time since to go back to those machines... I worked around the problem by providing Hens with a customized jar in which the JAXP detection was commented out... Conclusion: I think CML on MSFT JVM is currently broken. But a fix is known. Egon |