Hi Param,

The approach john mentioned(auhor the WSDL ourselves before creatig
service) is somewhat like the "contract-first" service development. Under
such development routine, you create the webservice through the following
steps:

* Define XML Schema for elements that will be transfered in the webservice
SOAP request/response message
* define the WSDL document for your webservice (with the XML schema defined
above)
* generate webservice code that can produce SOAP message conforms to the
above WSDL/xml schema

the highlight of this approach is that the producted service will conform
to our predefined XML schema and WSDL. Thus, it provides good
interopability for heterogenious platforms to communication through the
webservice. Because the client and server can create service and proxy
through the predefined XML schema/WSDL.

Here are some articles introducing Contract-First service
development and how it works in ASP.NET asmx webservice:


#Contract-First Service Development
http://msdn.microsoft.com/msdnmag/is...tation/default...


#Techniques for Contract-First Development
http://msdn.microsoft.com/msdnmag/is...erviceStation/


#Enrich Your XML Serialization With Schema Providers In The .NET Framework
http://msdn.microsoft.com/msdnmag/is...ontract/defaul...

Hope this also helps some.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



This posting is provided "AS IS" with no warranties, and confers no rights.

Those links should be:
http://msdn.microsoft.com/msdnmag/is...assToContract/
http://msdn.microsoft.com/msdnmag/is...erviceStation/
http://msdn.microsoft.com/msdnmag/is...erviceStation/

Dwight Walker

"Steven Cheng[MSFT]" <stcheng (AT) online (DOT) microsoft.com> wrote

On Sun, 01 Apr 2007 10:52:52 -0400, Dwight Walker <dwight (AT) wwwalker (DOT) com.au>
wrote:

this is wonderful