We are in the process of upgrading to Tomcat 3.2.1 from 3.1 and have experienced an issue with class loading which we did not see before. We started getting class not found exceptions while trying to do a naming lookup to a Weblogic 510 sp8 server. Under 3.1 this was not an issue. We placed the weblogic .jar files in our WEB-INF/lib dir and everything was groovy. Setting the classpath upon startup of tomcat seems to fix the problem on Windows 2000. However, doing so on Linux (RH 6.2) results in Class Cast exceptions which we do not see with Tomcat 3.1 against the same deployed code base. Anyone help or pointers are appreciated. Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
