Peter Donald wrote: >The security permissions for the JVM are only used for the common classes (ie >$PHOENIX_HOME/lib/*.jar) and the container classes ($PHOENIX_HOME/bin/lib) > >However we actually specify the security policy as the one stored in the >phoenix-launcher.jar. Have a look in that for the Kernel/common classes >policy file. > yes - I had noticed it.
>However note. That because of the way Java security policys work the >permissions of an application can never exceed the permissions assigned to >the kernel as the permissions checked against are effectively an intersection >of the two sets. That make sense? > yep. One further question on setting policies in environment.xml. How can one grant a permission, say to a default domain, ie without specifying the codebase? The most obvious way would be to omit the code-base attribute in <grant> but phoenix complains upon initialisation that code-base is null. I did look in the code and it does allow for the null code-base case. Thanks, Mauro -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
