Re: [Joelib-devel] Is joelib.jar compatible with applet?

[Takayuki K. <t-k...@ni...>]

Dear Joerg 

Thank you for early reply.

>Please check those classes and hack them if necessary. I assume that some
of the security settings might not be correct, so you >should maybe also
check Java-Applet security issues, but this is a general JavaApplet problem
and you should check Google and >SUN pages for that.

I am also using cdk.jar and JME.jar as applets and they work well. I think
that problem is not caused by Java-Applet security issues.

>Can you enable the debug mode in log4j.properties for
wsi.ra.tool.BasicResourceLoader wsi.ra.tool.BasicPropertyHolder.
I tried to modify log4j.properties and the following is log files.

[ERROR] wsi.ra.PropertyHolder                    - Propertyfile
joelib.properties not found.
java.lang.ExceptionInInitializerError
	at chempropapp.setStr(chempropapp.java:44)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at sun.plugin.javascript.invoke.JSInvoke.invoke(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at sun.plugin.javascript.JSClassLoader.invoke(Unknown Source)
	at sun.plugin.com.MethodDispatcher.invoke(Unknown Source)
	at sun.plugin.com.DispatchImpl.invokeImpl(Unknown Source)
	at sun.plugin.com.DispatchImpl$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.plugin.com.DispatchImpl.invoke(Unknown Source)
Caused by: java.security.AccessControlException: access denied
(java.lang.RuntimePermission exitVM)
	at java.security.AccessControlContext.checkPermission(Unknown
Source)
	at java.security.AccessController.checkPermission(Unknown Source)
	at java.lang.SecurityManager.checkPermission(Unknown Source)
	at java.lang.SecurityManager.checkExit(Unknown Source)
	at java.lang.Runtime.exit(Unknown Source)
	at java.lang.System.exit(Unknown Source)
	at wsi.ra.tool.PropertyHolder.instance(PropertyHolder.java:281)
	at wsi.ra.tool.PropertyHolder.instance(PropertyHolder.java:258)
	at joelib.io.IOTypeHolder.loadFileTypes(IOTypeHolder.java:537)
	at joelib.io.IOTypeHolder.instance(IOTypeHolder.java:192)
	at joelib.molecule.JOEMol.<clinit>(JOEMol.java:239)
	... 16 more
java.lang.Exception: java.lang.ExceptionInInitializerError
	at sun.plugin.com.DispatchImpl.invokeImpl(Unknown Source)
	at sun.plugin.com.DispatchImpl$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.plugin.com.DispatchImpl.invoke(Unknown Source)

Thanks in advance.


Takayuki KOTANI


-----Original Message-----
From: joe...@we... [mailto:joe...@we...] 
Sent: Friday, September 08, 2006 4:06 AM
To: t-k...@ni...; Joe...@li...
Subject: AW: [Joelib-devel] Is joelib.jar compatible with applet?

Dear Takayuki,

first the Webstart application is deprecated and uses a pretty old JOELib
version, but this is just a site note.

Second, all descriptors/features and file formats are defined in the
joelib.properties file. Therefore, this an extremely important property
definitions file.
I still do not know from the messages provided what is going wrong. Can you
enable the debug mode in log4j.properties for
wsi.ra.tool.BasicResourceLoader wsi.ra.tool.BasicPropertyHolder

Those are the relevant classes for getting and loading the properties.
Usually those classes should be able to get the data from String, URL, and
File resources.

I had also already some problems with those classes, especially when working
in combination with other projects and dependencies. Anyway, this is a
powerful outsourcing of parameters and avoids hard coded (hidden) features,
so it is worthwhile solving this.

Please check those classes and hack them if necessary. I assume that some of
the security settings might not be correct, so you should maybe also check
Java-Applet security issues, but this is a general JavaApplet problem and
you should check Google and SUN pages for that.

Please let me know, if this message was helpful and what the status of your
problem is.

Joerg