At my current job we have some client applications that are using Microsoft's Soap Tool Kit 2.0. I am not clear on what functionality it provides, but they (Microsoft) claim it defaults to document based web services and that it is more "scalable" (that word should be banned). Having our clients build up xml documents is much more painful and I would rather avoid this. This leads up to a bunch of questions...
1. Does Soap Toolkit 2.0 provide a way to interact with Soap RPC? Client side code generation?
2. From the Java client side, it is definitely easier to interact with Soap RPC. Does that hold true for Microsoft?
3. Any reason Soap Toolkit 2.0 would default to document based?
4. Besides some incompatibility issues that we have need to worry about, are there any other issues with using Soap RPC.
5. Any known gotchas using weblogic WSDL gen capabilities to provide the WSDL's to Microsoft based clients?
- Chris
1. Does Soap Toolkit 2.0 provide a way to interact with Soap RPC? Client side code generation?
2. From the Java client side, it is definitely easier to interact with Soap RPC. Does that hold true for Microsoft?
3. Any reason Soap Toolkit 2.0 would default to document based?
4. Besides some incompatibility issues that we have need to worry about, are there any other issues with using Soap RPC.
5. Any known gotchas using weblogic WSDL gen capabilities to provide the WSDL's to Microsoft based clients?
- Chris