Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP .Net Web Services > Adhering to a particular WSDL - basics

Thread Tools

Adhering to a particular WSDL - basics

Posts: n/a
Hi !
Am writing a webservice that will be called by another web service. Now, I
understand that we have to agree on a contract before the two web services
can talk to each other. How should I proceed?

I've been given a WSDL specifying the types and messages. Now, how do I
write my webservice such that it adheres to this WSDL?

One use case is:
Client will call my web service requesting for a list of employees. I'm
retrieving the records from my DB and now have to send it back to the
client. There is a type in the WSDL that defines "Employee". So, do i have
to define a class in my code matching this type definition in WSDL? After
that do I just serialize the employee record into xml and send it back to
the client?

Any samples/links to samples will be helpful !


Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
webservices, wsdl & xsd (schema-2-wsdl) Dark Java 1 11-14-2008 07:58 PM
wsdl.exe fails with WebMethods generated wsdl file mrnu ASP .Net Web Services 0 06-07-2004 04:51 PM
WSDL file produces useless class when imported with WSDL.exe RH ASP .Net Web Services 1 05-27-2004 09:40 PM
is the w3c's schema for wsdl and wsdl/soap binding possibly buggy ? _clb_ Chris Bedford XML 0 08-20-2003 11:52 PM
WSDL.EXE: WSDL Import Directive Stephen Edgecombe ASP .Net Web Services 0 08-13-2003 06:38 AM