Ulf Dittmer wrote:
For example, you can't deploy a war file with a web service on Apache Tomcat.
Why not? Axis is a web app, so it can be part of any war file you care to deploy.
All that is needed to deploy a WS is a servlet container that supports whatever version Servlet API version is required by whatever SOAP stack you happen to use. For example, if you're using Metro (or the JAX-WS reference implementation, or Axis 2), then Tomcat 5.5 running on Java 5 will do nicely.
Ulf is right. I meant, Apache Tomcat by itself is NOT a web service container. It is a Servlet container. To run web services on it, you will have to 'package' the web service container (e.g. Axis) along with your application.
Sounds like the original probelm is this: the web hosting provider is making Tomcat available to the website it is hosting. Based on what I have seen in the past, the hosting provider is probably making WEB-INF (for classes) and webapp (for
JSP) available in your account. You want to deploy a war file that has web service in it.
If I understood your problem correctly, you need to create a war file with your application, package Axis libraries along with your war file and drop the file in WEB-INF in your account. Finally, if you don't know already, ask your hosting provider for the URL to access your servlets/JSPs, which will determine the web service URL as well. Finally, I would start with a simple servlet/JSP before dropping a war with a web service in it.
Hope this helps.