Each Web Application gets its own private class loader.
A class loader can only see classes loaded/loadable by it and by its parents.
The Two Web Applications are siblings, independant from each other.
I think you should give each WebApplication a complete set of its own classes so that you can upgrade each independantly.
Brendan
-----Original Message-----
From: E B
To: [EMAIL PROTECTED]
Sent: 10/15/01 9:04 PM
Subject: webapps' classpath
I am using apache soap 2.2 with tomcat 3.2.1.
There seem to be 2 classpaths, one tomcat's
and the other webappp's WEB-INF/classes.
For a SOAP service class, which of these two
is visible first ?
which of the two is recommended and why ?
I have two web-app's: A1 and A2. (A2 is soap).
I want to refer A1's objects in A2's class.
But A1's classes are not visible to A2. why ?
I had to put A1's classes in tomcat's classpath
to get it working.
thanks.
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
