Web Services Interoperability Technologies (WSIT, aka Project Tango), integrated in GlassFish V2, is an implementation of key WS-* specifications and provides first-class interoperability with Microsoft .NET 3.0 framework. Here is a collection of quotes from developers, media and partners endorsing WSIT in the past few months.

1. Microsoft, Sun Do Web Services Interoperability Tango (Personal blog, May 15, 2007) - The key message is: Developers are happy with WSIT.

Finally, a simple prove that Microsoft and Sun has been continuing their own "peace" agreement. More power to software developers!

2. Microsoft discusses Interop at JavaOne (TheServerSide, May 11, 2007) - They key message is: Most customers use both .NET and Java, look to WSIT for interop.

The Web Service Interoperability Technology (WSIT) is an interesting initiative, because it is primarily between .NET 3.0 and Java EE 5.0. ... primary users ... are early adopters. WSIT will become more interesting in the future, when more companies move to the technologies.
When you want to do reliable messaging and transactions that span tech borders, [BP 1.1] does not go far enough. WSIT goes beyond the basic profile to make sure we do all of the open standards, but adds secure token exchange and transfer across technology boundaries, and we test our technology against those.
We have found that about 70-90% of our customers have both .NET and Java in their systems... WSIT improves ease of use in deploying interoperable applications.

3. Takes two to Tango: Java Web Services and .NET Interoperability (Personal blog, May 11, 2007) - The key message is: Complexity hidden by NetBeans/WSIT plug-in, Convincing demo: Excel -> JavaEE

I must say I was quite convinced by the WSIT demo, which used an Excel/.NET client to invoke a JEE web service deployed in Glassfish. From the developer point of view, the complexity of adding reliable delivery, security, etc seems to be completely hidden by the Netbeans plug-in, so developing interoperable web services might not be a complete nightmare after all. The project is still very young, but I find it very promising.

4. Tango Day at JavaOne: .NET 3.0 dances with Sun GlassFish (TheServerSide, May 10, 2007) - The key message is: Integrate with .NET via GlassFish/Tango, Excel to back-end Unix

Sun show[ed] how easy it was to integrate .NET 3.0 and Sun Glassfish applications using Web Services Interoperability Technology, blockquote named Tango
The presentation gave a demonstration of how it was possible to use a Microsoft Excel application as a client to post data to a back end server ... running on Unix.

5. Sun Shines On WS-* Integration (SDTimes, Feb 1, 2007) - The key message is: Sun engineers work with MS engineers on-site in Redmond, Microsoft calls WSIT best impl of WS-* outside its own

Chutzpah was the word most used to describe Sun Microsystems' Redmond emissaries. When eight of Sun's enterprise Java engineers flew up to Washington state to collaborate with Microsoft's engineers, many industry watchers trotted out that venerable Yiddish word, which, loosely translated, means gall.
But as these two teams worked together to bring about some calm in the turbulent seas of Web services, they found that engineering knows no prejudice. The result, three years later, is Sun's Web Services Integration Technology, and Microsoft has called it the best implementation of the WS-* standards outside of its own.

6. Project Tango (Redmond Developer News, Feb 2007) - The key message is: Microsoft "supports" Tango, Microsoft says GlassFish/Tango enables communication with .NET.

Working with Microsoft engineers, Sun has developed Project Tango, a set of Web services interoperability standards -- WSIT for short -- which the company says will ensure a happy marriage between the Java platform and WCF.
Gartner analyst Nick Gall says ensuring clean interoperability between Java and WCF clearly holds value for both companies. "There's no question the Microsoft community will flock to [WCF]. It's the unified communications architecture for environments that are .NET-centric," he says. "... The question is, if I heavily use WCF, and if I use its default settings, will I be automatically interoperable with the JEE world? There, the question mark is really big.
A Microsoft spokesperson noted that Project Tango "is a Sun initiative and Microsoft supports the initiative."
Jorgen Thelin, Microsoft's senior program manager for interoperability standards, offered general praise for the effort: "The combination of .NET Framework 3.0 with Sun's Glassfish and Tango technologies enable high-fidelity communication between the Java and .NET Framework 3.0."

7. State of Web services. Interoperability (JRoller, Jan 5, 2007) - The key message is: Interoperability is the main criteria to evaluate a Web services framework.

Interoperability should be the main criteria when you evaluate a Web Services framework.
Any serious Web Services framework should ship with interoperability examples/tests demonstrating all four combinations of Java and .NET clients and services calling each other.
... Java client to call Java service does not have much value.
The only framework that lists interoperability with .NET as a top priority and ships some interoperability .NET examples is WSIT.
Terms of Use; Privacy Policy; Copyright ©2013-2017 (revision 20160708.bf2ac18)
Please Confirm