Re: Using the .NET WebService tools

From: Dino Chiesa [Microsoft] (dinoch_at_online.microsoft.com)
Date: 07/27/04 

Date: Tue, 27 Jul 2004 17:04:34 -0400

the XSD.exe tool can be used to help map between .NET classes and XML files.
(This is called XML Serialization). The XSD.exe tool can read a W3C XML
Schema (XSD file) and produce a class definition that corresponds to that
schema. Instances of that class can then be serialized to instances of XML
documents that conform to the schema.

A WSDL file is a definition of a webservices interface. Think of a
webservice as a bit of logic that accepts a message, does something, and
then replies with another message. The WSDL file describes the messages
that the webservice accepts and returns (among other things). Typically
these messages are defined in (you guessed it) XML Schema. The WSDL file
can internally contain the schema for the incoming and outgoing messages,
or, the WSDL file can reference an external Schema (a separate XSD file)
that defines these things.

WSDL.exe is a tool that slurps in WSDL files and produces either:
  - a client side proxy
  - a server-side skeleton

The proxy is a class that your app could use to invoke the webservice
described by that WSDL file.
The skeleton is something you would use if you wanted to implement a
webservice that conformed to the given WSDL file. You are probably not
doing that. 

----
SOAPSUDS.exe is for adding SOAP support to .NET Remoting - it sounds like
you don't want that here.
The scenarios I have seen are:
  you get a WSDL file
  run it through wsdl.exe to produce a proxy
  build a client-side app that instantitates the proxy, then calls methods
on it.
Note when you use wsdl.exe on a WSDL file that references one or more
external XSD files, you usually have to include the WSDL file and all XSD
files on the command line, eg:
  wsdl.exe TheInterface.wsdl   Schema1.xsd Schema2.xsd
-Dino
"Gary Dunne" <KeepYourSpam.Gdunne@zarion.com.deletethis> wrote in message
news:%23pIMoZ$cEHA.3096@tk2msftngp13.phx.gbl...
> I have been provided with a set of wsdl files to create a  number of web
> services. Each wsdl file also has a corresponding XSD file.
> I've been looking at the various .NET tools that can be used to generate
> webservices (XSD.Exe, WSDL.Exe SoapSuds etc) but I'm still at a loss.
>
> Can someone please confirm the following points:
>     XSD is used to create Serialized code that forms the webservice server
> code.
>     WSDL is used to create the classes that can consume a webservice
>     SOAPSUDS can be used to create the classes that can consume a
webservice
> through Remoting
>
> Thanks
>
> Gary
>
>

Relevant Pages

  • Re: Using the .NET WebService tools
    ... This appears to be an excerpt from a client-side proxy class. ... client-side proxy class into a server-side webservice. ... If you want to generate a service from a WSDL file, ... > Public Function ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Using User-Defined Data Type
    ... WebService" you essentially invalidate the proxy you created. ... The WSDL file is then used on the client for generating "Proxy ... just deal with "objects" in your code on both Server & Client side. ... >web reference defination and reference my document dll file, ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Returning Dataset or Datatable via Web Service
    ... hand tuning of the XML schema and the WSDL file are specifically those ... Our own client application. ...
    (microsoft.public.dotnet.framework.webservices)
  • PHP5 SOAP and https
    ... I have a problem with Soap class in PHP5. ... webservice Wsdl file, which the ...
    (comp.lang.php)
  • Re: Sharing Types between Webservice and Client
    ... The wsdl file contains the right namespaces. ... >> I've also created a client application that consumes this webservice. ...
    (microsoft.public.dotnet.framework.webservices)