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=14622>. 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=14622 Jasper fails when security manager is set by a jsp [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-11-17 19:52 ------- The bug is not necessarily with who sets SM, but with the way Jasper checks whether there's a SM installed or not. At first, it checks it via System.getSecurityManager(), and then it simply assumes securityManager is already set, but that assumption is too weak. When Jasper loads a class after securityManager's initialization, and System.getSecurityManager() returns not-null value, the variable - securityManager is still null, but Jasper doesn't care about it - that's the bug. The jsp is just example, and in fact would have been anything that sets SM. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
