Someone mentioned that 1.4 will allow for runtime config of security 
policy... why not defer tight policy integration until we have switched 
to it by default?

Could also add njar to the system loader...

It seems very strange to me that we now have huge names under tmp/deploy 
(which may not fully get removed... or do we scan down to tmp/deploy and 
delete parent directories when a deployment goes away) to get a security 
policy to work.  It just seems very strange...

--jason


Scott M Stark wrote:

>The njar url cannot be used in a security policy file as a codebase
>because the njar protocol handler is not available when the
>security system initializes:
>
>policy: Adding policy entry:
>policy:   signedBy null
>policy:   codeBase
>njar:file:D:/usr/local/src/cvsroot/Main/jboss-all/build/outpu
>t/jboss-3.0.0beta2/server/default/tmp/deploy/D/usr/local/src/cvsroot/Main/jb
>oss-
>all/build/output/jboss-3.0.0beta2/server/default/deploy/-
>java.security.Policy: error adding Entry
>sun.security.provider.PolicyParser$GrantEntry@2498b5
>java.net.MalformedURLException: unknown protocol: njar
>
>To work with a security manager the custom protocols must be available
>at startup using the java.protocol.handler.pkgs property.
>
>xxxxxxxxxxxxxxxxxxxxxxxx
>Scott Stark
>Chief Technology Officer
>JBoss Group, LLC
>xxxxxxxxxxxxxxxxxxxxxxxx
>
>
>_______________________________________________
>Jboss-development mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/jboss-development
>



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to