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

B

Bill Sempf

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
 
J

John Saunders

Bill Sempf said:
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.

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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,743
Messages
2,569,478
Members
44,899
Latest member
RodneyMcAu

Latest Threads

Top