commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LOGGING-107) AccessController use
Date Sun, 19 Nov 2006 09:21:39 GMT
     [ http://issues.apache.org/jira/browse/LOGGING-107?page=all ]

Simon Kitching resolved LOGGING-107.
------------------------------------

    Fix Version/s: 1.1.1
       Resolution: Fixed

> AccessController use
> --------------------
>
>                 Key: LOGGING-107
>                 URL: http://issues.apache.org/jira/browse/LOGGING-107
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Simon Kitching
>             Fix For: 1.1.1
>
>
> A problem has been reported with 1.1 by Aaron Bruegl on 6/6/06. An AccessControlException
is being thrown in an applet invoked from javascript even when the logging lib has been signed
and granted permissions.
> LogFactoryImpl.java:1250 in the 1.1 release has this line:
>             // try the parent classloader
>             currentCL = currentCL.getParent();
> which does seem to be a likely cause for the exception.
> This code should be executed under an AccessController, so that granting the logging
jar the appropriate permissions can fix the problem; without this, all calling code also needs
to have that permission.
> Maybe we should wrap method discoverLogImplementation in an AccessController, covering
all cases like this?

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message