cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helma van der Linden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-125) Java SecurityManager java.lang.RuntimePermission createSecurityManager required for cocoon 2
Date Tue, 25 Oct 2005 13:15:55 GMT
     [ http://issues.apache.org/jira/browse/COCOON-125?page=all ]
     
Helma van der Linden closed COCOON-125:
---------------------------------------

    Resolution: Fixed

closed with resolution = fixed

> Java SecurityManager java.lang.RuntimePermission createSecurityManager required for cocoon
2
> --------------------------------------------------------------------------------------------
>
>          Key: COCOON-125
>          URL: http://issues.apache.org/jira/browse/COCOON-125
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.0
>  Environment: Operating System: All
> Platform: All
>     Reporter: Glenn Nielsen
>     Assignee: Cocoon Developers Team

>
> The class org.apache.cocoon.util.log.CocoonLogFormatter$CallStack
> extends java.lang.SecurityManager.  The comments for this class
> indicate that this is a hack to get a stack trace as an array of
> classses.  But if you are running Cocoon 2 in a servlet container
> such as Tomcat with the Java SecurityManager enabled this requires
> that you grant the java.lang.RuntimePermission createSecurityManager
> to cocoon in your policy file  This is a dangerous permission to grant.
> This needs to be changed so that extending java.lang.SecurityManager
> is not needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message