Its not reasonable to force the use of 1.4 at this point so the first point is irrelevant. We have to be able to run under a security manager with 3.0 with JDK 1.3.
Adding the njar protocol handler to the system classpath does not solve the problem as the policy file parser crashes with a stack overflow error. I don't know if this can be fixed. I don't want to force the use of a custom security policy implementation as this requires modification of the JDK installation. 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, March 01, 2002 2:43 AM Subject: Re: [JBoss-dev] njar protocol is not working with security manager > 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 > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
