We have this same issue and have found it easier to copy the contents of axis into both a webapps/myapp AND into the webapps/axis directory. We do NOT leave copies in tomcat's common/lib. The reason for this is to insure that use always use separate classloaders. It also means that if you move the webapps/axis code to another machine, you are less likely to have problematic dependencies. This might end of solving your clashing-logging lib file problem too, since tomcat's classloader wont "see" axis's logging jar file.
-Adam
-----Original Message-----
From: Shrotriya, Sumit [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 09, 2003 9:35 AM
To: [EMAIL PROTECTED]
Subject: Using Axis and Servlets..any Ideas !!
Hi All,
I am trying to run my application which is a servlet and uses Axis in
Tomcat4.1.18. Now the way I want to configure the Tomcat set up is
something like this
/webapps/axis
/MyApp
Thus neither axis nor my application are consuming each other.
The data flow would be something like this
Client--->MyApp--->Axis--->MyAppService--->Axis--->Client
Please dont advise me otherwise...I know the glitches of this
approach...its a requirement...
Problems faced so far
a) Need to duplicate the code and the jar files both of my application
and axis in the common/lib dir. I think cos Axis and MyApp cant talk
shoulder to shoulder.
b) Tomcat4.1.18 has a common-logging-api.jar file which clashes with the
common-logging.jar file from axis.(As the have some files common)
If someone has implemented their system in this fashion, please do let me
know. All your ideas and feedback are welcome..
Thank You,
~Sumit
