DataSet WSDL

[MarkAurit]

How does one go about getting the information from an .xsd file into a WSDL
document? I have a web service that creates a simple object that IBM
Websphere can see and use. Great.
However, when I expose a DataSet, Websphere cant use the WSDL document, as
it doesnt describe the data elments in the dataset. Im done a lot of
readying and looking at posts, and typed datasets sounds like they might be
the answer, but I cant figure out how to information from the .xsd into the
WSDL document.
Thanks, Mark

[Dino Chiesa [Microsoft]]

Don't use typed datasets.
Instead use an XSD schema that maps to custom objects. Think of them as
Data Transfer Objects (from GoF).
You can pass arrays and graphs of objects this way, with full interop,
between WebSphere and .NET.

To answer your question,
do a wsdl:import on the XSD .
example:

http://webservices.xml.com/2003/08/0...ockquote3.wsdl

article:

"MarkAurit" <Ma*******@disc ussions.microso ft.com> wrote in message
news:5E******** *************** ***********@mic rosoft.com...

How does one go about getting the information from an .xsd file into a
WSDL
document? I have a web service that creates a simple object that IBM
Websphere can see and use. Great.
However, when I expose a DataSet, Websphere cant use the WSDL document, as
it doesnt describe the data elments in the dataset. Im done a lot of
readying and looking at posts, and typed datasets sounds like they might
be
the answer, but I cant figure out how to information from the .xsd into
the
WSDL document.
Thanks, Mark

[Elena Kharitidi]

The Web Services framework has special knowledge of Datasets and typed
DataSet: WS recognizes them by checking the IXmlSerializabl e implementation:

public interface IXmlSerializabl e {
/// <include file='doc\IXmlS erializable.uex '
path='docs/doc[@for="IXmlSeria lizable.GetSche ma"]/*' />
XmlSchema GetSchema();
/// <include file='doc\IXmlS erializable.uex '
path='docs/doc[@for="IXmlSeria lizable.ReadXml "]/*' />
void ReadXml(XmlRead er reader);
/// <include file='doc\IXmlS erializable.uex '
path='docs/doc[@for="IXmlSeria lizable.WriteXm l"]/*' />
void WriteXml(XmlWri ter writer);
}

During wsdl generation WS calls the IXmlSerializabl e.GetSchema() method, if
it returns null WS assume that the type is a DataSet and uses predefined
schema for it:

<xs:element name="DSRespons e">
<xs:complexType >
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="DS5Result ">
<xs:complexType >
<xs:sequence>
<xs:element ref="xs:schema" />
<xs:any />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence> </xs:complexType>
</xs:element>

If the method returns a valid XmlSchema object, WS assume that the type is
a typed DataSet, and the schema object should be used for generating the
typed dataset on the client. The schema is added to the service
description document and referenced via <wsdl:import> statement where the
namespace=".." attribute is set to the XmlSchema.Targe tNamespace, and the
WS uses a different instance schema:

<xs:element name="ReturnTyp edDSResponse">
<xs:complexType >
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="ReturnTyp edDS1Result">
<xs:complexType >
<xs:sequence>
<xs:any namespace="http ://tempuri.org/TypedDataSet1" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

The client side recognizes the schema patterns:
1. if the complex type has only two elements, and the first one is a
reference to a schema element and the second one is <any/> --> then this
complex type is a DataSet
2. if the complex type has one element, and it is <any /> with a namespace
attribute, then this is a typed DataSet and the schema with targetNamespace
matching the namespace attribute value should be used to generate source
code for it.

Thanks,
Elena