Originally posted by Mark Secrist:
When you say it generates RPC stubs & skeletons, what do you mean. The big difference in document vs rpc is what is passed to the web service. The stubs and skeleton code will actually look pretty much the same. So, the difference is in what defines the types being exchanged. With rpc, it is the native langauge the service is implemented in. If you use encoding, the SOAP envelope will try to help, which is where much of the performance hit comes from. With Document style exchanges, the types are defined using XML schema(s) and tends to provide a bit more flexibility in terms of the kind of information being exchanged.
Hope this helps.
Mark
I am referring to the code generated from Axis compared to what used to be generated from Apache SOAP 2.2.
Basically, when you use the wsdl2java tool in Axis, you get a Service interface, a stub, and a bunch of serializable classes. You get this regardless of the style (document or rpc).
My question is- why do I need this serialization when using the document style? It seems like overkill. Is this because Axis is now JAX-RPC compliant?
Using Apache SOAP 2.2 on a document wsdl, you don't get the serializable classes or the remote interfaces, you only deal with the Message class.
I am questioning this because I am seeing significant performance problems using Axis over Apache SOAP for 'document' style web services.
The code produced by SOAP 2.2 is getting results back about 4x faster.
[ July 02, 2003: Message edited by: Chad McGowan ]