tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Brunkow <>
Subject RE: Apache-Soap and Tomcat 3.3
Date Thu, 15 Nov 2001 17:21:01 GMT
Thanks for the response.

I only want my web application to respond to SOAP requests.  The soap files
are in my web app.  The problem is, they still have to be in the Server
classpath.  My Toplink classes won't work if they are in the Server
classpath, so says experience and the Toplink vendor.  That means, I can't
use soap and toplink together. Why in the world the Soap people have allowed
this restriction is beyond me.  The Tomcat path is only for the running of
the server, why you need to add classes to it, to run my application is just
plain wrong.


-----Original Message-----
From: Tom Drake []
Sent: Tuesday, November 13, 2001 4:25 PM
To: Tomcat Users List
Subject: Re: Apache-Soap and Tomcat 3.3


Another solution is to simply deploy the apache web-application into the
same context as your own. This means that you have to merge web.xml
files, but it's otherwise pretty straightforward.

This means that only your web-application will be able to respond to
SOAP requests, however.

I've implemented Apache SOAP both ways.

----- Original Message -----
From: "David Brunkow" <>
To: "'Tomcat Users List'" <>
Sent: Tuesday, November 13, 2001 3:35 PM
Subject: Apache-Soap and Tomcat 3.3

| Does anyone have Apache-Soap working with Tomcat 3.3? Unless you jar your
| app and put it in %TOMCAT_HOME%\lib\common\ I don't think it should work.
| I'm having all kinds or problems with classes could not be found on just
| samples.
| Thanks,
| Dave

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message