> Hi there,
>
> In the document I fount on web site
http://download.microsoft.com/download/1/b/b/1bb6e11f-8e8c-46bf-a2d7-9a16976d452
6/NETConnectedLogoTechnicalSpec020904.doc,
> it says that "To be .NET Connected compliant, a Web services application
> must use the HTTP transport and the Document/Literal SOAP style. (A
> document-based service uses an XML Schema to define the format for the
> request and response of the service. A literal message stores each parameter
> in its own element. Such well-described data offers the highest level of
> interoperability.)" What does it mean? Does it mean the WSDL file?
[WilliamT] Yes, your WSDL File does reflect to the parties involved that
your messages much send over messages RPC-Encoding style
If it
> does, how can I define the format for the request and response of the service
> in the WSDL file during compiling the web service project (I'm using
Visual
> Studio .NET)? Thanks for any help.
>
> Yolande
[WilliamT] VS.NET uses Doc-Literal by default, so there is really nothing to
add or do. If you should want to use RPC, you just add the SoapRpcMethod
attribute
hth.

Signature
Thank you.
Regards,
William T (Softwaremaker)
http://www.softwaremaker.net/blog
=========================================
Yolande - 21 Feb 2005 16:48 GMT
hi William,
Thank you very much for the help. As I'm new to WSDL, I wonder how to use
the modified WSDL file which includes my own schema. According to the
specification "Web Services Description Language (WSDL) 1.1", I import my
schema into the WSDL generated by "http://localhot/Service1.asmx?wsdl" . But
I don't know how to use the new WSDL (Service1.wsdl) for my Web Service. When
I go to http://localhot/Service1.asmx, the web service still uses the
Service1.asmx?wsdl but not Service1.wsdl. Any help?
Thank again.
Yolande
> > Hi there,
> >
[quoted text clipped - 26 lines]
>
> hth.
Softwaremaker - 22 Feb 2005 00:24 GMT
This is just one of the few things I disagree with the RAD-approach style of
VS.NET in generating WSDL for the Web Services.
Take note of these steps:
1) Turn off HELP Documentation of asmx (so it doesnt get too smart and
generate the WSDLs)
<webServices>
<protocols>
<remove name="Documentation" />
</protocols>
</webServices>
2) Have some kind of communication channel to show your consumers the newly
generated WSDL. You can use a combination of approaches such as an off-line
out-of-band approach, so just have some default page that shows the WSDL. I
personally recommmend the use of UDDI (tModel deployment) for this BUT it
may be a bit too much for a simple deployment.
hth.

Signature
Thank you.
Regards,
William T (Softwaremaker)
http://www.softwaremaker.net/blog
Independent Microsoft Regional Director | Microsoft MVP - Solutions
Architect
=========================================================
> hi William,
>
[quoted text clipped - 13 lines]
> > >
> > > In the document I fount on web site
http://download.microsoft.com/download/1/b/b/1bb6e11f-8e8c-46bf-a2d7-9a16976d452
6/NETConnectedLogoTechnicalSpec020904.doc,
> > > it says that "To be .NET Connected compliant, a Web services application
> > > must use the HTTP transport and the Document/Literal SOAP style. (A
[quoted text clipped - 21 lines]
> >
> > hth.