As reported earlier, Metro team from Sun participated in the fourth (third, second, first) Microsoft Interop Plugfest. Microsoft is working on .NET 3.5 (codename Orcas) and the focus this time was to ensure that there are no regressions with WSIT 1.0. Read Harold’s report for more details.
Technorati: webservices metro plugfest glassfish microsoft interoperability
Has any interop testing been done with duplex communications using the wsDualHttp binding?
Comment by Chuck Rianhard — July 30, 2007 @ 5:53 am
The protocols used in wsDualHttp binding are not defined by any of the WS-* specs and so no interop testing is done on this binding.
Comment by Arun Gupta — July 30, 2007 @ 4:37 pm
[Trackback] Based upon a user request, I’ll explain why wsDualHttpBinding (a system-provided binding in WCF) is not an interoperable binding. This blog entry will explain the service endpoint code, client code, generated WSDL and the SOAP messages exchanged based …
Comment by Arun Gupta's Blog — August 2, 2007 @ 11:07 am
Chuck, I’ve posted an article that explains why wsDualHttpBinding is not interoperable at:
http://blogs.sun.com/arungupta/entry/wshttpdualbinding_a_non_interoperable_binding
Comment by Arun Gupta — August 2, 2007 @ 11:09 am
Has any interop testing been done with duplex communications using the wsDualHttp binding?
Comment by LAPTOP BATTERY — November 27, 2008 @ 5:21 pm
wsHttpDualBinding is a non-interoperable binding as explained at:
http://blogs.sun.com/arungupta/entry/wshttpdualbinding_a_non_interoperable_binding
and so no interop testing has been done.
Comment by Arun Gupta — November 28, 2008 @ 7:01 am