|
From: Leif M. <le...@ta...> - 2003-02-13 08:29:57
|
Another user had had a similar problem last summer. It is a permission problem. When you run the app on its own, only your class needs permission, but when run under the java, your class's main method are actually called by the Wrapper code. This means that the Wrapper.jar classes also need to be given permission. Take a look at this thread: https://sourceforge.net/forum/forum.php?thread_id=697368&forum_id=122338 Here was the result from that thread: -------------------- Ok, I got it working. The problem was simply that the wrapper classes need to be granted Permission to be able to access the privileged classes in the RMI service. I created the following policy file called rmiserver.policy: --- // Give Wrapper classes full permissions grant codeBase "file:../lib/wrapper.jar" { permission java.security.AllPermission; }; --- Then by using the following settings in wrapper.conf, it all seems to work correctly. --- wrapper.java.mainclass=com.silveregg.wrapper.WrapperSimpleApp wrapper.java.classpath.1=../lib/wrapper.jar wrapper.java.additional.1=-Djava.security.policy=../conf/rmiserver.policy wrapper.app.parameter.1=sun.rmi.registry.RegistryImpl --- All other properties have their default values. ------------------- Try adding the above to your policy file and write back with the results. Cheers, Leif |