WSIT and WCF Plugfest

"I" in WSIT stands for
Interoperability. To ensure WSIT is interoperable with .NET 3.0, WSIT engineers
made a third visit to Microsoft headquarters in less than a year. Microsoft
hosted the third
plugfest at their campus and Sun Microsystems
showed up to test WSIT and GlassFish
interoperability with their upcoming .NET 3.0 stack.

Harold, Mike,
Jiandong, Joe, Ken and myself (all
from Sun) "wsited" Microsoft last week.
We were just representations of the bigger team and effort scattered all over
the globe (Santa Clara, Burlington, Salt Lake City, Portland, Prague, Germany,
France, Bangalore). And then there were some engineers doing remote testing as
well.

As mentioned earlier,
WS-Addressing functionality in JAX-WSA
is cleaned up and now an integral part of  JAX-WS
2.1 RI. That has been my focus for the past few weeks. So in this plug-fest,
I took our JAX-WS 2.1 RI for interop on WS-Addressing test cases. Microsoft has
caused a few interop problems with WS-Addressing in the past (Member
Submission policy assertion namespace change, incorrect
Action from WCF client, WS-Addressing
WSDL namespace change). But this time everything worked, it just worked. And
that's what is out-of-the-box
interoperability.

Other than that, we had a good success rate doing interop on WS-Atomic
Transactions, WS-Reliable Messaging, WS-Secure Conversation, WSS 1.0 and 1.1,
WS-Trust. We achieved interop on composite scenarios like Secure Reliable
Messaging and Secure MTOM. And this interop is two-way meaning that WCF client
invoke WSIT endpoint and WSIT client invoke WCF endpoint.

We care about "I", the most, in WSIT. GlassFish
v2 now integrates WSIT bits on a regular basis. When GlassFish v2 goes
final, be assured it will be interoperable with .NET 3.0 framework shipping in
Windows Vista and other platforms.

Read about our success stories from first
and second
plugfests.

Technorati: WSIT Tango
Web Services
Interoperability Indigo
WCF GlassFish
Dotnet