It would get used by specifying the following properties:
-Djava.security.manager -Djava.security.policy=policyURL

to the vm at startup. These properties can be set after vm
startup, but this does not work well in all cases due to some
static initialization code in the 1.3 classes. Setting up JBoss
to run with a security manager is a change the user will have
to make to the start script.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- 
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, February 22, 2002 3:23 PM
Subject: Re: [JBoss-dev] Configuration layout changes...


> Off topic (a little), but where soes server.policy get used?
> 
> Is there a way to setup a policy after starting the vm.  I know that you 
> can do this from the cl, but I am not aware of a way to do it afterwards.
> 
> If not, then we have a small problem, as the scripts which start up the 
> vm do not know anything about the final destination where configuration 
> lives and certainly can not donload files from URLs.
> 
> Do you know if the above (second paragraph) is possible?  We may be 
> doing something like that already?
> 
> If not, then I think we will need to setup a local configuration dir to 
> store these bits (plus the non-script bits from bin/).
> 
> --jason
> 



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

Reply via email to