Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <7588442.1180021036623.JavaMail.jira@brutus>
Date: Thu, 24 May 2007 08:37:16 -0700 (PDT)
From: "Carsten Ziegeler (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2068) Add failover for loading classes.
In-Reply-To: <25879943.1180015157751.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498683 ] 

Carsten Ziegeler commented on COCOON-2068:
------------------------------------------

I'm not quiet sure, but you could perhaps set the thread context class loader to the class loader you need. Cocoon itself uses the thread context class loader in all places, so if you set this before you call Cocoon, it should work i think.

> Add failover for loading classes.
> ---------------------------------
>
>                 Key: COCOON-2068
>                 URL: https://issues.apache.org/jira/browse/COCOON-2068
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: * Cocoon Core
>    Affects Versions: 2.1.10
>            Reporter: solprovider
>            Priority: Minor
>
> The ClassLoader from currentThread.getContextClassLoader() was unable to retrieve classes in my environment.  Add fallback to standard Java class loading.
> NOTE: The two "set" lines would work in either order.  I believe Cocoon is using a custom ClassLoader to dynamically load changes so the custom method must be tried first.  (The auto-reload ability will be lost for environments using the fallback, but at least they will be able to use Cocoon.)
> public class ClassUtils{
>    public static Class loadClass(String className) throws ClassNotFoundException{
>       Class ret;
>       try{
>          ret= ClassUtils.getClassLoader().loadClass(className);
>       }catch(ClassNotFoundException e){
>           ret= Class.forName(className);
>      }
>       return ret;
>    }
> }

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