Dear users,
I'm setting up a page that uses Jmol-JSO syntax (13.1.6)

I see that there are defaults for Info that suit the unsigned applet but not 
the 
signed applet.
This code works: 

var myInfo = {
        jarFile: 'JmolAppletSigned0.jar',
        jarPath: '.',
        isSigned: true
};
var myJmol = Jmol.getApplet("myJmol", myInfo);

but this one does NOT work:

var myInfo = {
        isSigned: true
};
var myJmol = Jmol.getApplet("myJmol", myInfo);

giving a Java  ClassNotfoundException error for JmolApplet.class 

I would expect that setting the 'isSigned' value should be enough for the 
correct jarfile to be used. In addition to that being simple and expected, 
otherwise, what is the purpose for the isSigned parameter if I must anyway 
specify the signed jar file? 

Clarification:
Apparently the unsigned version is trying to be used (according to 
debug:true). Since I had not included a copy of the unsigned jar files, I am 
getting the error. When all the files are present, the applet opens unsigned 
even though isSigned is set true.
 


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users

Reply via email to