> For example, have you tried expanding *all* the JAR files that ship with
> Tomcat and then re-assembling them into your single kunagi.jar?
This is exactly what I do. And my JNLP requires all-permissions. My application
can open ports, read and delete all files - but not start the embedded Tomca
> > Shouldn't there be a switch in Tomcat to turn off this checks?
>
> Why? If you don't want the Security Manager, don't turn it on.
I don't, WebStart does. Usualy when I turn on a feature in software A, I don't
expect it to affect software B. Logging for example can be configured
separately.
> On 26/03/2012 11:12, Witoslaw Koczewski wrote:
> >> There's a file called catalina.policy in tomcat/conf, which has some
> >> rules in it. You'll need compare those rules to the ones implemented in
> >> the client's policy file to work out wh
> There's a file called catalina.policy in tomcat/conf, which has some
> rules in it. You'll need compare those rules to the ones implemented in
> the client's policy file to work out what you need to add.
Since I am using embedded Tomcat, there is no catalina.policy :-(
Can't I just disable the
Hello,
for our Kunagi Java web application we have a signed kunagi.jar file which
contains our classes together with classes from embedded Tomcat 6. This runs
perfectly when calling java -jar kunagi.jar.
But when starting it with Java WebStart, I get an exception while embedded
Tomcat is start