jeudi 21 janvier 2010

WSIT between Java & .Net

I just like to inform you in this article, the existence of the WSIT "Web Services Interoperability Technologies".

WSIT specification was thought in order to handle and ensure interoperability of web services in the enterprise technologies scope. Sun, Microsoft ... and other technology pundits work together on several subjects, such as message optimization, reliable messaging, security ...
WSIT handle differents features aggregate many topics in high level categories, for example:

- SOAP, MTOM, WS-addressing are aggreated in "Optimization" purpose.
- WS-ReliableMessaging, WS-Coordination, WS-AtomicTransactions are grouped into "Reliability" subject.
- "Bootstrapping" category containt WSDL, WS-Policy, WS-MetadataExchange topics.
- "Security" handler WS-Security Policy, WS-Security, WS-Trust and WS-SecureConversation

Thank to DotNet France, I have publish a simple course about ".NET WCF and Java Interoperability", available here:

Julien Dollon in his vision asked to me, a presentation about these communication technologies. The goal was not to start a controversy or a fight, but to really show the ease of communication.

In this article I use WCF (Windows Communication Foundation) in .NET 3.5 and Metro in Java . These two technologies are based on standards interoperability has been really easy to implement, but in order to adding quality of service and .NET interoperability to Metro I recommend you throw an eye on the WSIT specification.

Why ? because, even these two Web Services Stacks (WCF .NET and Metro Java) are well-built, different interoperability problems can be appear, for example the Java long, double ... are broader than long, double in .NET

2 commentaires:

  1. Interesting topic, isn't it :)

    Since you are looking at Web Services Interoperability, you might want to take a look at the Apache Stonehenge project which demonstrates practical SOA interoperability across platforms (.NET, PHP, Java) with Apache open source projects using Web Services standards (more detail here

    JC Cimetiere (Microsoft)

  2. this sounds like a good thing! I'll see