From: Otis R. <osr...@ch...> - 2010-11-08 16:04:02
|
Angel, et al- I don't know if this is relevant, but when I had the problem with 1.6.0_22, I saw a number of blogs, including one at Oracle, that indicated a cookie problem related to security and 1.6.0_22. I was in a hurry trying to track down a Jmol issue, so I did not want to take the time to mess with Oracle and 1.6.0_22. I just backed of to 1.6.0_21. I should note that my security problem with 1.6.0_22 was with the unsigned applet. I should also note that the files were being served, not loaded via local directory path. This was not a typical local problem associated with an attempt to load a molfile via a local path. My local server should have served those files without the security violation. Jmol under 1.6.0_22 was not allowed to load them - under 1.6.0_21, all was well. Otis Otis Rothenberger chemagic.com On 11/8/2010 10:39 AM, Angel Herráez wrote: > Might be something with my system, but I am seeing it at both > computers, and with different applets (Jmol unsigned, my campus > Blackboard environment, among others). Also in different browsers. > > The warning jumps most often saying it's jmolApplet0.jar, but some > times it has been another component. Might it be the localization > module? > |