"Service not found" faults

[Ted Neward <Te...@matmail.ucdavis.edu>]

I've got a simple project (I took the AddressFetcher and switched it over to
doc/literal), yet when I run it, the server faults with "service not found".

Am I mistaken in understanding that doc/literal is supposed to key off of
the SOAPAction header? If that's a correct understanding, then why isn't it?
:-)

(I can ship the project--.jar file of both client and server--if somebody
wants to verify.)

Ted Neward
Architect, UCDavis Account & Financial Services
http://www.javageeks.com
http://www.clrgeeks.com
 

Re: "Service not found" faults

[Sam Ruby <ru...@apache.org>]

Ted Neward wrote:
> 
> Am I mistaken in understanding that doc/literal is supposed to key off of
> the SOAPAction header? If that's a correct understanding, then why isn't it?
> :-)

Axis must determine the service before it can even be aware of whether 
the service is doc/literal or rpc/encoded or whatever.

One can imagine any number of transport specific mechanisms to determine 
the service, but for now, I will focus on the three mechanisms which 
ship with Axis that are applicable to the HTTP transport.

SOAPAction is certainly a way, but with SOAP 1.2 it becomes increasingly 
deprecated.

The namespace of the first XML element in the body is another mechanism, 
and is the one used by Apache SOAP.

The URL itself is a third mechanism, and is the one that I would 
recommend.  Assuming your service is located at 
http://host/axis/yourService, simply ensure that the WSDD file used to 
deploy your service contains <service name="yourService" ...>.

If you are generating your server side bindings from WSDL, then ensure 
your wsdl contains <port name="yourService" ...>.

- Sam Ruby