D
Don C
1. Is there a 2nd way to declare a strongly typed DataSet (e.g.
CustomerDataSet) in WSDL instead of using the WSDL <import
namespace="CustomerDSnamespace" location="url to CustomerDS.xsd"/>?
Apparently, if I include CustomerDataSet schema definition in WSDL types, it
will not be recognized as a DataSet by .NET WSDL compiler when a Web
Reference is created. I have to use the WSDL import statement. What do I
need to do to make it recognize the CustomerDataSet definition in the WSDL
types. The CustomerDataSet has the correct definition (ie isDataSet=true)
and does work with the WSDL import.
2. How to send a strongly typed DataSet over SOAP without the XSD?
I found that when I am sending a strongly typed DataSet (e.g.
CustomerDataSet) instance over SOAP, I still need to send its XSD with the
CustomerDataSet every time. Otherwise, .NET will not parse attribute data
type right even though, the XSD is available as part of the strongly typed
DataSet (ie CustomerDataSet). This defeats the purpose of using the strongly
typed DataSet between Web service server and client. Is there a way not to
send the XSD?
Thanks,
Don
CustomerDataSet) in WSDL instead of using the WSDL <import
namespace="CustomerDSnamespace" location="url to CustomerDS.xsd"/>?
Apparently, if I include CustomerDataSet schema definition in WSDL types, it
will not be recognized as a DataSet by .NET WSDL compiler when a Web
Reference is created. I have to use the WSDL import statement. What do I
need to do to make it recognize the CustomerDataSet definition in the WSDL
types. The CustomerDataSet has the correct definition (ie isDataSet=true)
and does work with the WSDL import.
2. How to send a strongly typed DataSet over SOAP without the XSD?
I found that when I am sending a strongly typed DataSet (e.g.
CustomerDataSet) instance over SOAP, I still need to send its XSD with the
CustomerDataSet every time. Otherwise, .NET will not parse attribute data
type right even though, the XSD is available as part of the strongly typed
DataSet (ie CustomerDataSet). This defeats the purpose of using the strongly
typed DataSet between Web service server and client. Is there a way not to
send the XSD?
Thanks,
Don