You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Gary L Peskin <ga...@firstech.com> on 2000/12/07 18:52:56 UTC

[Fwd: Re: [Fwd: Re: [C2][Xalan2J] Extension Handler Error with Fix (wazRe: [C2]: Namespace bug in XalanTransformer)]]

Martin --

I've forwarded this to Dims regarding your second paragraph.  If Dims
concurs, I'll make the change as you suggest in your paragraph three.

Thanks,
Gary

-------- Original Message --------
Subject: Re: [Fwd: Re: [C2][Xalan2J] Extension Handler Error with Fix 
(wazRe: [C2]:  Namespace bug in XalanTransformer)]
Date: Thu, 7 Dec 2000 17:43:47 +0000 (GMT)
From: Martin Klang <ma...@pingdynasty.com>
To: Gary L Peskin <ga...@firstech.com>



hi Gary,

do you know what servlet engine Dims is using?
with tomcat, the ContextClassLoader will be their AdaptiveClassLoader,
which will check for classes in the system classpath first (if i
remember
correctly).
thus with tomcat, you should have the option of putting your extensions
in
either anywhere in the system classpath, tomcats lib _or_ the webapps
lib.

it would be interesting to know a bit more about what causes the context
classloader to fail (i'd cc this to Dims but can't find his email
address
right now).

i guess that what you're suggesting is to try Class.forName if loadClass
fails, but don't reset getCCL to null so that it will still try the CCL
first next time around - right? sounds reasonable, can't see why not.

/m