DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7052>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7052 Security manager not initialised or accessed properly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-03-20 12:48 ------- After further review the situation you reported is not a bug and the patch will not be applied. A SecurityManager can only be set once within a single instantiation of the JVM. What SecurityManager to use and the security policies to use are something that should be set by the container at startup, not by an application running within the container. The problem that you need to resolve is how to start JBoss with a SecurityManager and the security policies you need implemented for RMI. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
