SERVICES 
Hello Anne,
Thanx for the help. 
While reading WSDL 1.1 recommendation I found that WSDL schema
however suggests that the WSDL attached should be OK.
Refer to Schemas (Appendix 4.1) section of the standards.
 .......................
 .......................
<element name="binding" type="wsdl:bindingType"/> 
   <complexType name="bindingType"> 
      <complexContent> 
   <extension base="wsdl:startWithExtensionsType"> 
   <sequence> 
   <element name="operation" type="wsdl:binding_operationType"
minOccurs="0" maxOccurs="unbounded"/> 
  </sequence> 
      <attribute name="name" type="NCName" use="required"/> 
      <attribute name="type" type="QName" use="required"/>  <--------
   </extension> 
  </complexContent> 
  </complexType> 
 ....................... 
 .......................

Please correct me if my understanding is wrong.
Thanks and Regards
Ravi

 --- Anne Thomas Manes <atmanes@[...].com>  wrote: 
>  The type attribute belongs in the <wsdl:binding> element, not in
>  the
>  <wsdl:operation> element. .NET wsdl.exe is just being forgiving,
>  but
>  the WSDL is in error.
>  
>  See http://www.w3.org/TR/wsdl#_bindings:
>  
>  The grammar for a binding is as follows:
>  
>  <wsdl:definitions .... >
>      <wsdl:binding name="nmtoken" type="qname"> *
>          <-- extensibility element (1) --> *
>          <wsdl:operation name="nmtoken"> *
>             <-- extensibility element (2) --> *
>             <wsdl:input name="nmtoken"? > ?
>                 <-- extensibility element (3) --> 
>             </wsdl:input>
>             <wsdl:output name="nmtoken"? > ?
>                 <-- extensibility element (4) --> *
>             </wsdl:output>
>             <wsdl:fault name="nmtoken"> *
>                 <-- extensibility element (5) --> *
>             </wsdl:fault>
>          </wsdl:operation>
>      </wsdl:binding>
>  </wsdl:definitions>
>  
>  The name attribute provides a unique name among all bindings
>  defined
>  within in the enclosing WSDL document.
>  
>  A binding references the portType that it binds using the type
>  attribute. This QName value follows the linking rules defined by
>  WSDL
>  (see section 2.1.2).
>  
>  Regards,
>  Anne
>  
>  On Tue, 01 Feb 2005 09:35:11 -0000, raviheg <raviheg@[...].com>
>  wrote:
>  > 
>  > 
>  > Hello All,
>  > I have been trying to generate java clients using IBM's websphere
>  and
>  > C# client using .NET. Websphere throws non-confirmance of WSDL
>  > error,but .NET succesfully consumes the WSDL and generate C#
>  client stubs.
>  > WSDL
>  > -----------------
>  > ...
>  > ...
>  > ...
>  >  <soap:binding style="document"
>  >    transport="http://schemas.xmlsoap.org/soap/http"/>
>  >    <operation type="def:EDADHPOC" name="EDADHPOC">
>  >     <soap:operation soapAction="EDADHPOC"/>
>  >     <input name="inEDADHPOC
>  > ...
>  > ...
>  > ...
>  > 
>  > Websphere throws error :
>  > Attribute 'type' not allowed to appear in element 'operation'.
>  > 
>  > I went through the WSDL 1.1 standards and could not find much
>  help
>  > regarding this.
>  > Could someone please confirm if this WSDL is as per WSDL 1.1
>  standards.
>  > Regards
>  > Ravi
>  > 
>  > -----------------------------------------------------------------
>  > This group is a forum for the discussion of the WSDL
>  specification and its implementation.  Please stay on-topic.
>  > Yahoo! Groups Links
>  > 
>  > 
>  > 
>  > 
>  >
>   

________________________________________________________________________
Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/


-----------------------------------------------------------------
This group is a forum for the discussion of the WSDL specification and its implementation.  
Please stay on-topic. 
Yahoo! Groups Links

<*>  To visit your group on the web, go to:
    http://groups.yahoo.com/group/wsdl/

<*>  To unsubscribe from this group, send an email to:
    wsdl-unsubscribe@[...].com

<*>  Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/