BP 1.1 Conformance
JAX-WS 2.0 enforces strict Basic Profile 1.1 compliance. The following are known cases where .NET framework does not enforce strict BP 1.1 semantics and their usage can lead to interoperability problems.
BP 1.1 R2211
In
rpclit
mode, BP 1.1http://www.ws-i.org/Profiles/BasicProfile-1.1-2006-04-10.html
, R2211 disallows the use ofxsi:nil
in part accessors (see the R2211 for the actual text). From a developer perspective this means that inrpclit
mode, JAX-WS does not allow a null to be passed in a web service method parameter.//Java Web method public byte[] retByteArray(byte[] inByteArray) { return inByteArray; } <!-- In rpclit mode, the above Java web service method will throw an exception if the following XML instance with xsi:nil is passed by a .NET client. --> <RetByteArray xmlns="http://tempuri.org/"> <inByteArray a:nil="true" xmlns="" xmlns:a="http://www.w3.org/2001/XMLSchema-instance"/> </RetByteArray>