|
> From: Narayanan R Pillai > > That message looked too familiar, so I looked at the response on my server > when I used a partial HTTP Request, ie > http://servername:8080/sanjose/services. When I try the above, I only get a "not found" (404) message. If I use the service name (http://servername:7080/WSServer/services/Service1). I also note that you're using port 8080, while my service is set up to run on port 7080. Is that something you changed? > This link http://www.w3.org/TR/soap12-part0/#L26854 might come in handy > though. This is good information, but it doesn't seem to apply. I can't figure out how to get the server to respond to a simple GET request. > The web service was generated with all default parameters and a look at > the wsdd gives the following for the method that I was talking about : I used the WDSC web service wizard, and it didn't create a WSDD, only a WSDL. How confused am I here? > pps: would you consider running axis within Websphere, to have this > functionality ? :) I may do that, although the ethereal port sniffer is doing a GREAT job so far. It has definitely confirmed my assumption that the request is being wrapped as a SOAP document, as well as the response. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.