You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/10/09 14:58:31 UTC

[jira] Created: (SLING-1145) Exceptions from dynamic class loader providers should be catched

Exceptions from dynamic class loader providers should be catched
----------------------------------------------------------------

                 Key: SLING-1145
                 URL: https://issues.apache.org/jira/browse/SLING-1145
             Project: Sling
          Issue Type: Improvement
          Components: Commons
    Affects Versions: Commons ClassLoader 1.0.0
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: Commons ClassLoader 1.0.2


If a dynamic class loader provider throws some unexpected exception like a NPE this exception is not catched inside the class loader facade but propagated up the call stack. Therefore a single malicous provider can bring down the whole class loading.
Those exceptions should be catch, logged and ignored

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

[jira] Resolved: (SLING-1145) Exceptions from dynamic class loader providers should be catched

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1145.
-------------------------------------

    Resolution: Fixed

Fixed in revision: 824328

> Exceptions from dynamic class loader providers should be catched
> ----------------------------------------------------------------
>
>                 Key: SLING-1145
>                 URL: https://issues.apache.org/jira/browse/SLING-1145
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons ClassLoader 1.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Commons ClassLoader 1.0.2
>
>
> If a dynamic class loader provider throws some unexpected exception like a NPE this exception is not catched inside the class loader facade but propagated up the call stack. Therefore a single malicous provider can bring down the whole class loading.
> Those exceptions should be catch, logged and ignored

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

[jira] Closed: (SLING-1145) Exceptions from dynamic class loader providers should be catched

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-1145.
-----------------------------------


> Exceptions from dynamic class loader providers should be catched
> ----------------------------------------------------------------
>
>                 Key: SLING-1145
>                 URL: https://issues.apache.org/jira/browse/SLING-1145
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons ClassLoader 1.0.0
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Commons ClassLoader 1.1.0
>
>
> If a dynamic class loader provider throws some unexpected exception like a NPE this exception is not catched inside the class loader facade but propagated up the call stack. Therefore a single malicous provider can bring down the whole class loading.
> Those exceptions should be catch, logged and ignored

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