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.
Dave -----Original Message----- From: Tom Drake [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 4:25 PM To: Tomcat Users List Subject: Re: Apache-Soap and Tomcat 3.3 David: 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" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> 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 the | samples. | | Thanks, | | Dave -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
