not the parameters. So still confused. Only needed for Google
2003-05-30 Miguel de Icaza <[email protected]>
* Methods.cs (MethodStubInfo): Start support for RPC style as well
as Literal style. Take an object instead of a
SoapDocumentMethodAttribute, and allow the value to be also a
SoapRpcMethodAttribute. Pull data from both.
Kill SoapBindingUse, we only use this during validation.
Turn out Google uses RPC/Literal, and its a good demo.
svn path=/trunk/mcs/; revision=15014
a Soap invocation.
The result is still not handled though.
2003-05-29 Miguel de Icaza <[email protected]>
* SoapHttpClientProtocol.cs (CreateMessage): Kill. Move
functionality to Invoke.
(Invoke): Use new TypeStubInfo/MethodStubInfo instead.
* SoapClientMessage.cs: Drop old mechanism, use MethodStubInfo instead.
* Methods.cs: New file. Contains the managed for TypeStubs and
MethodInfoStubs.
A MethodInfoStub contains the serializers we use for the SOAP
request.
* SoapClientMessage.cs: Drop parameters from the clientmessage, it
does not belong here. Drop oneway, we canextract that from the
SoapDocumentMethodAttribute class that we pass.
svn path=/trunk/mcs/; revision=15003