WSIT and WCF Plugfest

Guest Author
"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
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

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

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
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

Technorati: WSIT
Interoperability IndigoWCF

Join the discussion

Comments ( 4 )
  • Arun Gupta's Blog Thursday, October 19, 2006
    [Trackback] Read Jorgen's interview on The Server Side about how the Interop plugfests at Microsoft are arranged. There is full section talking about WSIT and WCF interoperability towards the end of the interview. As mentioned in my previous plugfest reports (1,...
  • Arun Gupta's Blog Thursday, July 19, 2007
    [Trackback] 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...
  • Arun Gupta's Blog Tuesday, April 1, 2008
    [Trackback] Microsoft BizTalk R11 CTP was released last week and now contains a sample that is based on GlassFish, Metro and NetBeans. Even though today is April 1st, this is not intended to be an April Fool's Day joke. Read...
  • aion kinah Friday, March 5, 2010

    I have an answer on your problem. The reason why it's doesn't work if the application is launched as JNLP, is that ClassLoader loads all modules as 'fixed' modules. But fixed module cannot change its state nor be uninstall. That's why OperationContainer.canBeAdded() will return false for JNLP launched module thus adding such modules for operation DIRECT_DISABLE is invalid and will throw IllegalArgumentException: Invalid module for operation DIRECT_DISABLE.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.