> 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" ...>. > I double-checked, and portType is definitely named; but surely you don't mean to imply that I should be definining a separate URL per operation of the port of the service (that is, I'm only allowed one operation per portType)? That would be a horrible thing if it were the case....
Again, has ANYBODY gotten a doc/literal service to work with Axis, and if so, can they send me what they've got? Ted Neward Architect, UCDavis Account & Financial Services http://www.javageeks.com http://www.clrgeeks.com -----Original Message----- From: Sam Ruby [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 01:44 To: [EMAIL PROTECTED] Subject: Re: "Service not found" faults 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
