Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / October 2006

Tip: Looking for answers? Try searching our database.

Creating a Xml Web Service contract from an XSD and lots of coffee

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bill Sempf - 10 Oct 2006 19:05 GMT
I have a XSD that describes a standard (IEEE) implementation of a contract
and related objects.  I need to create a web service that implements the XSD.
I realize that I can read the XSD and create it by hand, but that doesn't
seem to be the point.  It seems more reasonable that I chould just be able to
use the XSD as a cookie cutter to generate the WSDL - or, more accurately,
generate the ASMX code that generates the WSDL.

So my question is this: am I missing something?  Does VS2005 do this and I
am just missing it?  Is there a third party tool that does this really well
that I am lacking?

On that thought, I also need to make a database to hold the contents of the
objects in a relational fashion.  I can do this by hand too.  Should I have
to?  This is the 'back end' of the same process.  Shouldn't it at least be
semi-automated?

I'd appreciate any thoughts from anyone who knows more than me about this.

S
John Saunders - 10 Oct 2006 19:37 GMT
>I have a XSD that describes a standard (IEEE) implementation of a contract
> and related objects.  I need to create a web service that implements the
[quoted text clipped - 18 lines]
>
> I'd appreciate any thoughts from anyone who knows more than me about this.

The XSD file isn't enough to specify a web service contract. It may tell you
the shape of the messages, but it can't, for instance, tell you that
operation X accepts messages A and B as parameters, returns C and D as
results, or may produce faults F and G. It can't tell you about the service,
either.

The XSD can be referenced from a WSDL, and the WSDL can be used as input to
WSDL.EXE /SERVER to generate a server stub. You can inherit from this and
create your server.

John

P.S. Some compliance checkers I've used complain about using wsdl:import to
import a schema. Apparently, you're supposed to do something like put an
empty schema in the wsdl:types section, and have that schema include the
real one. Something like that.

I ignored the compliance checker and continued developing my web service
using wsdl:import! I'll "fix" it in a future release.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.