aspose file tools*
The moose likes Web Services and the fly likes Web service endpoint is hosed when deploying to tomcat using a war file Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Web service endpoint is hosed when deploying to tomcat using a war file" Watch "Web service endpoint is hosed when deploying to tomcat using a war file" New topic
Author

Web service endpoint is hosed when deploying to tomcat using a war file

Tony Ennis
Ranch Hand

Joined: May 22, 2003
Posts: 86
My war file is called myservice.war. The web service endpoint is myendpoint.

My intention is to be able to fetch my wsdl using http://localhost:8080/myendpoint?wsdl This works fine when I run using java6's built-in web service support. However, when I deploy the web service to Tomcat it requires:

http://localhost:8080/myservice/myendpoint?wsdl

While it works it obviously hoses my clients. Would someone know of a tomcat config change to allow me to specify the url? My web.xml is pretty explicit about the url being /myendpoint.

Thanks for any insight.

Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 39547
    
  27
You'd need to deploy the web app into the webapps/ROOT directory in order to use that URL.


Ping & DNS - updated with new look and Ping home screen widget
Tony Ennis
Ranch Hand

Joined: May 22, 2003
Posts: 86
Thanks very much. I was able to use the service as-is by setting the wsdl in the wsimport command. If my boss has a problem with it, then I'll ue your solution.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Web service endpoint is hosed when deploying to tomcat using a war file
 
Similar Threads
Can't see the WSDL file
How to put the WSDL location on Eclipse's Web service explorer?
custom wsdl
Error when calling a web service in Java Client
Problems with SOAPUI, SpringWS, and Tomcat5.5