> MS web services are document-styled web services. But you still have > >the overhead of (de)serializing your XML request to parameters.
> When you have a service which takes 5 parameters as input, you would >have to deal with the (de)serializing/mapping of the XML to 5 different >parameters. Instead if you want to map your XML request to a "Document" >object, you would be circumventing the overhead of these many >(de)serializations but you would have the overhead of custom >marshalling of the raw XML which I think is considerable.
Not! Deserializing 5 simpleTypes is damn fast. Since you'd have to do the same thing if you sax parsed I'd say its identical!
BTW, you don't have to deserialize the XML in ASMX based services at al.. You can consume the XML as a stream. Just write your [WebMethod] differently.
> I understand that Microsoft uses Doc-style as default SOAP binding. But how does the mapping of XML to COM objects occur? I have a very vague idea of Microsoft's web services, please correct me if I am wrong.
Whoa - IIRC, the COM based SOAP toolkit will be retired this summer and no longer supported. Not that its really that well supported now with great alternatives like ASMX and WSE 2.0.
M apping XML to CLR types occurs via the .NET Framework XMLSerialization stack which is plenty fast and a nice API I might say.
> Document styled web services in .NET differ only in the way SOAP requests are formatted BUT the underlying mechanism is similar to a RPC styled web service. In .NET web services you could use SOAP extensions to intercept the incoming SOAP requests and map them to objects.
I don't know what you're getting at.
ASMX (and Axis) uses wrapped doc/lit to married the worlds of RPC oriented consumption with literal wire format. The messages are entirely doc lit but the message schema is designed to mosel an RPC invokation that can be mapped comfortably to OO languages like Java and C#.
Jim Murphy Mindreef, Inc.
