You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/05/09 00:02:46 UTC

DO NOT REPLY [Bug 7052] - Security manager not initialised or accessed properly

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

mmansell@PureEdge.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
         Resolution|WONTFIX                     |



------- Additional Comments From mmansell@PureEdge.com  2002-05-08 22:02 -------
The code in JasperLoader caches the SecurityManager for no reason (that I can 
tell). Removing the cache as suggested by the last diff provides the ability 
for code to install a SecurityManager after the Jasper engine has initialized. 
This code may be an extension to Tomcat (via an interceptor) and doesn't have 
to be a web application. I don't see what the harm is in removing the cache, 
and I've personally run into a number of scenario's where having it causes 
problems.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>