You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2009/01/07 14:58:38 UTC

[jira] Closed: (TILES-324) Cannot call ClassUtil.setContextClassLoader() with SecurityManager

     [ https://issues.apache.org/struts/browse/TILES-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli closed TILES-324.
----------------------------------


Closed due to the release of Tiles 2.0.7.

> Cannot call ClassUtil.setContextClassLoader() with SecurityManager
> ------------------------------------------------------------------
>
>                 Key: TILES-324
>                 URL: https://issues.apache.org/struts/browse/TILES-324
>             Project: Tiles
>          Issue Type: Bug
>          Components: tiles-core
>    Affects Versions: 2.0.6
>            Reporter: Eddy Chan
>            Assignee: Antonio Petrelli
>            Priority: Critical
>             Fix For: 2.0.7, 2.1.1
>
>
> In org.apache.tiles.util.ClassUtil.instantiate(String, boolean), there are two calls to setContextClassLoader for the currentThread.  This causes an issue with a SecurityManager that does not grant the RuntimePermission.  In my situation, since this class is in the webapp, the second call to setContextClassLoader causes an issue, since it is in the finally clause.  Two workarounds:
> 1) Remove the calls to setContextClassLoader.  (Not sure the necessity here.)
> 2) Flag whether the first call to setContextClassLoader was originally done, and then conditionally call setContextClassLoader if it was done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.