I've not come across the use of encodingStyle as you have below. I've seen such an encodingStyle used for rpc/encoded, but not for document/literal. Is this just hand-edited WSDL? Maybe it is someone's way of tricking (or trying to trick) .NET into including xsi:type attributes for document/literal.
Scott Nichol ----- Original Message ----- From: "Bhushan Khanal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 24, 2002 7:05 PM Subject: SOAP Encoding question > Why do you need to specify http://schemas.xmlsoap.org/soap/encoding/ when > using document/literal encoding? I have seen WSDL's that look like ... > > <soap:operation > soapAction="http://example.com/GetLastTradePrice"/> > <input> > <soap:body use="literal" > namespace="http://example.com/stockquote.xsd"; > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </input> > > Is there any special processing SOAP requiring us to specify the encoding. > > Bhushan > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
