cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <d...@yahoo.com>
Subject Re: [Fwd: Re: [C2][Xalan2J] Extension Handler Error with Fix (waz Re: [C2]: Namespace bug in XalanTransformer)]
Date Thu, 07 Dec 2000 17:50:22 GMT
Gary,
No Problem. Please go ahead.

Please note that all our JAR files are already in WEB-INF\lib but the problem still happens
on
Tomcat 3.2. 

Also note that C2 has to work on all exising Servlet2.2 Engines. So we cannot rely on Tomcat4.0
only....

Thanks,
dims

--- Gary L Peskin <garyp@firstech.com> wrote:
> Dims --
> 
> Somehow you didn't get included in the reply list.  Also, if you concur
> with the reasoning below, I was wondering if I could just change the
> catch (ClassNotFoundError) to:
> 
> catch (ClassNotFoundError cnfe)
> {
>   result = Class.forName(className);
> }
> 
> I just didn't understand the reason for having another try / catch
> clause.  Perhaps I missed something.  If so, please enlighten me.
> 
> Thanks,
> Gary
> 
> -------- Original Message --------
> Subject: Re: [C2][Xalan2J] Extension Handler Error with Fix  (waz Re:
> [C2]: Namespace bug in XalanTransformer)
> Date: Thu, 07 Dec 2000 09:10:32 -0800
> From: Gary L Peskin <garyp@firstech.com>
> Organization: The Firstech Corporation
> To: xalan-dev@xml.apache.org
> CC: Scott_Boag@lotus.com, cocoon-dev@xml.apache.org
> References: <20001207155806.7210.qmail@web106.yahoomail.com>
> 
> Davanum Srinivas wrote:
> > 
> > Scott,
> > 
> > There was a change in org\apache\xalan\extensions\ExtensionHandler.java which is
affecting
> > Cocoon2. Extension Handler now tries to use getContextClassLoader to load the class.
This is
> > failing for the classes that we need for some reason. Here's a patch which helps.
Basically if
> the
> > class is not found by getContextClassLoader then just use Class.forName() as it
was earlier
> > (Java1).
> > 
> > Thanks,
> > dims
> > 
> 
> Dims --
> 
> The reason for this is that we now look to the ContextClassLoader, if it
> exists, to actually do the load.  This requires that your extensions
> move from the Xalan directory or .jar (or elsewhere in the CLASSPATH)
> into the appropriate directory for that ContextClassLoader.  I think in
> Tomcat this is called a Context.  Any extensions then, must be in the
> appropriate Tomcat Context.
> 
> With your change, if the extension is not found in the Context, we fall
> back to getting it from the Xalan .jar or system CLASSPATH.  Is this
> what you want or should we force users to move the extensions into the
> appropriate Context(s).  If this is truly what you want, I'll commit the
> change forthwith.
> 
> Gary


=====
Davanum Srinivas, JNI-FAQ Manager
http://www.jGuru.com/faq/JNI

__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

Mime
View raw message