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 91455 invoked from network); 30 May 2002 09:27:57 -0000 Received: from mel-o.alcatel.fr (HELO mel.alcatel.fr) (194.133.58.32) by daedalus.apache.org with SMTP; 30 May 2002 09:27:57 -0000 Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET) with ESMTP id g4U9S8xx012076 for ; Thu, 30 May 2002 11:28:08 +0200 Received: from bsf.alcatel.fr (mail205.dit.sxb.bsf.alcatel.fr [155.132.205.115]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id LAA18918 for ; Thu, 30 May 2002 11:28:07 +0200 (MET DST) Received: from bsbrest.bst.bsf.alcatel.fr (bsbrest [155.132.38.31]) by bsf.alcatel.fr (8.8.8+Sun/8.9.3) with ESMTP id LAA11686 for ; Thu, 30 May 2002 11:28:06 +0200 (MET DST) Received: from BRE04000027466 (BRE04-000027466 [155.132.38.60]) by bsbrest.bst.bsf.alcatel.fr (8.9.1b+Sun/8.9.1) with SMTP id LAA26312 for ; Thu, 30 May 2002 11:28:03 +0200 (MET DST) Message-ID: <001f01c20820$f7244440$3c26849b@BRE04000027466> From: "Jean-Marc Taillant" To: References: Subject: Re: AXIS BUG ? Date: Thu, 30 May 2002 23:28:39 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I tested all my wsdl generated file trought Cape Studio toolkit and all is ok!. I definitely think that XML Spy aren't following WSDL spec. Thanks, Jean Marc ----- Original Message ----- From: "Russell Butek" To: Cc: Sent: Wednesday, May 29, 2002 4:19 PM Subject: Re: AXIS BUG ? > These are not bugs. See my comments inline between ... > > Russell Butek > butek@us.ibm.com > > > "Jean-Marc Taillant" on 05/29/2002 08:41:06 > PM > > Please respond to axis-user@xml.apache.org > > To: , > cc: > Subject: AXIS BUG ? > > > > > Hi all, > I found several bugs in server sid generated WSDL ( invoked with the ?wsdl > option in the URL...). > I made tests with several tools ( XML spy ( soap debugger plug-in & > SOAP:Net from www.soaptoolset.com) and i find this: > > AXIS generate WSDL with " This syntax is not understanded by XML spy and SOAP:Net > > > > The "wsdl" prefix defines the namespace that the wsdl constructs are in. > This prefix is defined. The default namespace is the same as the "wsdl" > namespace, so strictly speaking, the "wsdl" prefix is not needed, but it is > not wrong to have it. > > > > SOAP:Net need name attribute in "definitions" element. > I found that AXIS does not include this attribute in WSDL. > > > > The spec says that the name attribute in definitions is optional. > > > > The AXIS version used is the last nightly build from 28/05/2002 > > Somewhere else, i try .Net wsdl.exe tool to generate client C# proxy and > all is Ok for MS. > > I think it a problem because AXIS need to be compliant with client side > toolkit. I know that there can be a xml spy & SOAP:Net problem ( i send > email to them) but there is no cost to include "name" attribute for > example. > > > > Sounds like xml spy and SOAP:Net aren't following the specs. > > We could certainly add a name, but what would it be? The portType or > service name? (there could be more than 1 portType or service in a single > definition). The file name? (this could be dynamic: > "http://service/service?wsdl" vs "c:/service/myservice.wsdl") Some > constant? (rather meaningless) If you're only concerned about what ?wsdl > gives you, then I think we'd be safe giving you the service name for the > definition name since there will be only one service generated. Right, > Rich? > > > > Regards, > > Jean Marc > > PS: > I send this mail to axis-dev because this mail come after a large number > of mail with no response. > > > > Sorry if we haven't responded to you. We've gotten rather overloaded, > lately. > > >