> ancestors -- that hasn't changed. So in Tomcat 3.3 the normal
> thing to do is to put Xalan and all extension classes in the
> common classloader, ${tomcat_home}/lib/common, just as in
... or in ${tomcat_home}/lib/apps, which is the same except
that the Tomcat servlet container classes can't see it. That's
probably better (precludes any JAXP conflicts between xalan.jar
and Tomcat's jaxp.jar). The Readme files in the various lib
directories of the Tomcat 3.3b1 distribution clear all this up
nicely.
Cheers,
- Gulli
- Re: extension functions and Tomcat Dmitry Beransky
- Re: extension functions and Tomcat Dmitry Beransky
- Re: extension functions and Tomcat Gary L Peskin
- RE: extension functions and Tomcat Gunnlaugur Thor Briem
- Re: extension functions and Tomcat Gary L Peskin
- RE: extension functions and Tomcat Dmitry Beransky
- Re: extension functions and Tomcat Gary L Peskin
- Re: extension functions and Tomcat Gary L Peskin
- RE: extension functions and Tomcat Gunnlaugur Thor Briem
- Re: extension functions and Tomcat Gunnlaugur Thor Briem
- Re: extension functions and Tomcat Dmitry Beransky
- Re: extension functions and Tomcat Gary L Peskin
- Re: extension functions and Tomcat Dmitry Beransky
- Re: extension functions and Tomcat Gary L Peskin
