All, Sorry... just noticed I pasted the wrong wsdl.exe dump for the WSDL I sent below. The proper wsdl.exe dump is:
Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'DictaphoneBinding' from namespace 'http://org.apache.axis2/'. - Unable to import operation 'processDictaphone'. - The element 'http://org.apache.axis2/xsd:processDictaphoneRequest' is missing. Thanks for your help, Paul Lessard P.S. SOA Editor is no longer available from Cape Clear. They replaced SOA with "Cape Clear Studio" which I believe costs money. There maybe links to archived versions of SOA somewhere but I haven't found any yet. -----Original Message----- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: [email protected] Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: > Hi all, > > > > I'm trying to use the wsdl.exe prog provided by the .Net SDK and I'm > getting some errors. Looking through past posts, this doesn't seem to > be the "tn1" name problem that others had. The error I'm getting is the > following: > > > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > > > Warning: Schema could not be validated. Class generation may fail or may > produce incorrect results. > > > > Error: Unable to import binding 'AdmitToDplBinding' from namespace > 'http://org.apache.axis2/'. > > - Unable to import operation 'admitToDpl'. > > - The element 'http://org.apache.axis2/xsd:admitToDplRequest' is > missing. > > > > > > > > I'm just starting out in Web Services, so I'm not very familiar with > WSDL files. Having said that, here is the auto-generated WSDL from > Axis2 (sorry it isn't spaced out nicely): > > > > <wsdl:definitions xmlns:ns1="http://org.apache.axis2/xsd"; > xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:tns="http://org.apache.axis2/"; > targetNamespace="http://org.apache.axis2/";><wsdl:types><xs:schema > xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:ns2="http://www.w3.org/2001/XMLSchema"; > xmlns:ns0="http://www.w3.org/2001/XMLSchema"; > xmlns:ns1="http://www.w3.org/2001/XMLSchema"; > ns1:elementFormDefault="qualified" > ns0:attributeFormDefault="unqualified" > ns2:targetNamespace="http://org.apache.axis2/xsd";> > > <xs:element ns0:name="processDictaphoneRequest"> > > <xs:complexType> > > <xs:sequence> > > <xs:element ns0:name="param0" ns1:type="xs:anyType" /> > > </xs:sequence> > > </xs:complexType> > > </xs:element> > > <xs:element ns0:name="processDictaphoneResponse"> > > <xs:complexType> > > <xs:sequence> > > <xs:element ns0:name="return" ns1:type="xs:anyType" /> > > </xs:sequence> > > </xs:complexType> > > </xs:element> > > </xs:schema></wsdl:types><wsdl:message > name="processDictaphoneResponseMessage"><wsdl:part name="part1" > element="ns1:processDictaphoneResponse" /></wsdl:message><wsdl:message > name="processDictaphoneRequestMessage"><wsdl:part name="part1" > element="ns1:processDictaphoneRequest" /></wsdl:message><wsdl:portType > name="DictaphonePort"><wsdl:operation > name="processDictaphone"><wsdl:input > message="tns:processDictaphoneRequestMessage" /><wsdl:output > message="tns:processDictaphoneResponseMessage" > /></wsdl:operation></wsdl:portType><wsdl:binding > name="DictaphoneBinding" type="tns:DictaphonePort"><soap:binding > transport="http://schemas.xmlsoap.org/soap/http"; style="document" > /><wsdl:operation name="processDictaphone"><soap:operation > name="operation" soapAction="processDictaphone" style="document" > /><wsdl:input><soap:body use="literal" > namespace="http://www.org.apache.axis2"; > /></wsdl:input><wsdl:output><soap:body use="literal" > namespace="http://www.org.apache.axis2"; > /></wsdl:output></wsdl:operation></wsdl:binding><wsdl:service > name="Dictaphone"><wsdl:port name="DictaphonePortType" > binding="tns:DictaphoneBinding"><soap:address > location="http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone"; > /></wsdl:port></wsdl:service></wsdl:definitions> > > > > > > Anybody have any ideas? It's probably something blindingly obvious, but > as said, I'm quite new to Web Services. > > > > Thank you, > > Paul Lessard --
