Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 90864 invoked from network); 28 Jun 2002 19:41:58 -0000 Received: from matmail.ucdavis.edu (128.120.135.200) by 209.66.108.5 with SMTP; 28 Jun 2002 19:41:58 -0000 Received: by matmail.ucdavis.edu with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Jun 2002 12:46:03 -0700 Message-ID: <627D621CC38ED511AF8300B0D0D1A4EE01FC53EA@matmail.ucdavis.edu> From: Ted Neward To: "'Hurst, Cyrus'" , "AxisList (E-mail)" Subject: RE: "Service not found" faults Date: Fri, 28 Jun 2002 12:45:59 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N How interesting.... When I compare Cyrus' deploy.wsdd against the one generated by WSDL2Java, I notice right off that the WSDL2Java-generated one uses the "Java:RPC" message provider, and Cyrus' very clearly uses "Java:MSG". Is this an Axis WSDL2Java bug? I would expect it to generate a .wsdd file using "Java:MSG" if the WSDL describes a doc/lit service, no? tkn -----Original Message----- From: Hurst, Cyrus [mailto:Cyrus_Hurst@tvratings.com] Sent: Friday, June 28, 2002 05:45 To: 'TedN@matmail.ucdavis.edu' Subject: RE: "Service not found" faults Hi Ted, I implemented a very simple message-based web-service and client with Axis Beta 2 . The client sends a soap message with an xml payload . The service returns a response with a receive date embedded in it . The 2 files are attached. Hope this helps.... Regards, -Cyrus -----Original Message----- From: Ted Neward [mailto:TedN@matmail.ucdavis.edu] Sent: Thursday, June 27, 2002 6:33 PM To: 'axis-user@xml.apache.org' Subject: RE: "Service not found" faults > 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 . > 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:rubys@apache.org] Sent: Thursday, June 27, 2002 01:44 To: axis-user@xml.apache.org 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 . If you are generating your server side bindings from WSDL, then ensure your wsdl contains . - Sam Ruby