atom feed11 messages in org.apache.tomcat.usersRe: Using Xalan 1.0.1 with Tomcat 3.1...
FromSent OnAttachments
Jam...@cardsetc.comJun 15, 2000 6:46 pm 
Gary SheaJun 15, 2000 10:53 pm 
Jam...@cardsetc.comJun 15, 2000 11:36 pm 
Gary SheaJun 15, 2000 11:55 pm 
Jam...@cardsetc.comJun 16, 2000 4:43 am 
Markus ColomboJun 16, 2000 4:58 am 
Steve WeissJun 16, 2000 7:00 am 
Jam...@cardsetc.comJun 18, 2000 4:07 pm 
Craig R. McClanahanJun 18, 2000 5:32 pm 
Jam...@cardsetc.comJun 18, 2000 5:54 pm 
NachoJun 19, 2000 1:20 am 
Subject:Re: Using Xalan 1.0.1 with Tomcat 3.1 - Classloader problems?
From:Jam...@cardsetc.com (Jam@cardsetc.com)
Date:Jun 18, 2000 5:54:30 pm
List:org.apache.tomcat.users

Nah ... just needing someone good at batch scripts to show us how it should be done.

Okay, now I am really confused...

Shouldn't the behaviour be;

1. Tomcat starts up. 2. Tomcat explodes an WAR files found in the $TOMCAT_HOME/webapps directory. 3. For each web application (ie apps in the $TOMCAT_HOME/webapps directory + those explicitly named in server.xml) 3a. Add each JAR in the $WEB_APP/WEB-INF/libs directory to the CLASSPATH. 3b. Add the $WEB_APP/WEB-INF/classes directory to the CLASSPATH.

From what I have been hearing, Tomcat doesn't do 3b very well on the NT platform. This explains my problem with trying to deploy my web app in the WAR file format.

Is my understanding correct? I feel that Tomcat IS doing what it should be, however Xalan is somehow subverting Tomcat's classloader to dynamically load some classes and therefore doesn't pick up the CLASSPATH Tomcat carefully builds at step #3a and #3b above. What I'd like to know is... can this happen or is it impossible for web application code to bypass the Tomcat classloader?

Regards, James W.