RESOLVED: WSIT and WCF Jun CTP Interop Bug
By arungupta on Jul 14, 2006
Even though the list of breaking changes from Feb
CTP to Vista Beta 2 and Vista
Beta 2 to Jun CTP are documented. The list is missing a "minor"
detail of changing the WS-Addressing
1.0 WSDL Binding namespace from
(same as SOAP
Binding namespace) to
(WSDL Binding CR namespace). As a result a user reported
interop problems between Jun CTP and WSIT.
I updated the namespace for WS-Addressing WSDL Binding in WSIT this morning. After deploying one of the JAX-WSA unit tests and invoking svcutil.exe to generate proxy, got the following warning:
Warning: The optional WSDL extension element 'UsingAddressing' from namespace 'http://www.w3.org/2006/05/addressing/wsdl' was not handled. XPath: //wsdl:definitions[@targetNamespace='http://example.org/wsaTestService2']/wsdl:binding[@name='wsaTestPortTypeBindingAddressingRequired']
Seems like this CTP completely ignores a standard W3C extension
element to indicate WS-Addressing on a binding/port. It generated the proxy
correctly but of course the client did not send expected WS-Addressing headers
and thus the endpoint faulted appropriately. Anyway, I specified
within a policy assertion, regenerated the proxy and invoked the client. The
server returned the response correctly and CTP client displayed the response in
WSIT is now again interoperating with Jun CTP.