>>But if they are in individual .jar files then it might be the case that >>all of the translation .jar files would have to appear in the 'archive' >>parameter to the applet/object tag. That would have a negative impact on >>Jmol.js and .html pages. >> > Ah ok, I see the problem. > I thought that the applet could decide by itslef to load a .jar file, > but I don't have much experience with applets.
Unfortunately, an applet cannot decide to load .jar files by itself. I believe the thinking was/is as follows: "The web page author should decide which .jar files are accessible to the web page. Otherwise, a .jar file could try to load lots of other .jar files that the page author was not aware of." Frankly, this strikes me as a rather silly restriction, since all .jar files would have to have come from the same web server. But admittedly I have not fully researched/thought-through all the security implications. I know that was the case with old browser JVMs. Recently (4 or 5 years ago?) there were changes to the structure of the .jar Manifest. These manifest changes included jar-file-indexing. Something tells me that this restriction may have been lifted as part of these changes. I will put this on my list of things to investigate. Miguel ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
