WS-I Profile: R1005 A MESSAGE MUST NOT contain soap:encodingStyle attributes on any of the elements whose namespace name is "http://schemas.xmlsoap.org/soap/envelope/". So in order to claim conformance to WS-I Profile Basic 1.0a all the examples in the SOAP 1.1 spec should be changed from: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> to <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/>? Can anybody clarify this? Thanks!
The SOAP 1.1 specification was created long before the WS-I BP 1.0a. At the time it was created RPC/Encoded messaging was considered the norm. Since that time RPC/Encoded messaging has proven inadequate for interoperability so its not supported by the WS-I BP 1.0a. So yes, any example in SOAP 1.1 note that uses RPC/Encoded messaging is not WS-I BP 1.0a conformant. Having said that, keep in mind that awareness of RPC/Encoded messaging and the fact that it is used in legacy Web service applications (that's a funny thought) is important. The J2EE 1.4 app servers are still required to support RPC/Encoded messaging, but if you deploy a Web service with that type of binding than it will not be WS-I BP 1.0a compliant. Remember that although the J2EE 1.4 vendors must support the BP, you are not required to deploy BP conformant Web services � it�s a good idea but no one is going to cut your fingers off if you don't.