You can freeze almost all of SOAP:: WSDL's objects.
The only exceptions are the objects used in parsing WSDL definitions itself - they cannot be frozen.
All the document/rpc literal/encoded discussion will cede with WSDL2.0: These variants are dropped in favour of an extensible operation style mechanism. SOAP:: WSDL can use WSDL definitions containing namespaces, and emits SOAP messages with namespace information.
However, rpc/encoded is still popular, especially for scripting languages like perl, python or php.
You should probably use SOAP:: Lite for rpc/encoded web services.
SOAP:: WSDL:: Manual:: FAQ - Frequently Asked Questions (and answers) Yes. You should - as always - apply common sense and take appropriate safety measures, especially if running SOAP:: WSDL as a server. Future versions of SOAP:: WSDL may require you to re-generate interfaces in order to use them. rpc/literal is RPC with named parameters, whereas rpc/encoded corresponds to positional parameters.
The difference between rpc and document is that rpc SOAP messages have an additional container named after the remote procedure called.
Occurrence, ordering, value-spaces, and identity constraints are not checked.
No, SOAP:: WSDL does not perform XML Validation (that is, validation against a DTD).WS-I prohibits the use of DTDs in WSDL definitions. The XML Specification does not require validation from XML processors.It states how validating and non-validating parsers must react on errors.as an underlying format for application data model more preferable.This chapter describes various performance tricks that allowed the author to write a very high-performing parser in C : pugixml.SOAP:: WSDL is not a conformant XML Schema processor in this sense, as it does not validate all XML Schema constraints. The SOAP1.1 note does not say anything about validation. specification explicitly states that XML Schema validation is not required for the SOAP envelope, and that applications may decide whether they need XML Schema Validation for the SOAP payload or not. specification does not mandate XML Schema validation.