Arun Gupta, Miles to go ...

Arun Gupta is a technology enthusiast, a passionate runner, and a community guy who works for Sun Microsystems.
« Previous day (Oct 18, 2006) | Main | Next day (Oct 20, 2006) »

http://blogs.sun.com/arungupta/date/20061019 Thursday October 19, 2006

JAX-WS 2.1, WS-Addressing, WSIT and GlassFish

JAX-WS 2.1 RI replaced JAX-WS 2.0.1 and JAX-WSA 1.0 EA2 in WSIT approximately 2 weeks ago. This is where I've been spending most of my time during the past few weeks. With this change, WSIT is now using WS-Addressing functionality natively provided in JAX-WS 2.1 RI is used instead of relying upon a pluggable JAX-WSA 1.0 EA2. This approach has several benefits as outlined earlier. A complete description of JAX-WS roadmap will help you understand the difference between the different version numbers.

Starting with GlassFish b22, this version of WSIT is also integrated in GlassFish. So, if you download GlassFish you get WSIT, JAX-WS 2.1 and all other great stuff. This is the very first integration of JAX-WS 2.1 RI in GlassFish and most of the functionality is working. I encourage you to download GlassFish b22 and give us feedback on how we can make it better for you.

Technorati: WSIT WS-Addressing JAX-WSA

del.icio.us | furl | simpy | slashdot | technorati | digg |
|

Interop Plugfest: Behind the curtains

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, 2, 3), we have incrementally achieved a very good level of interoperability with Microsoft. And this is also evident (Green and Yellow is good) in the slide used at Microsoft tracking WS-* adoption in the industry.

WSIT technologies are available in GlassFish.

Technorati: WSIT WCF

del.icio.us | furl | simpy | slashdot | technorati | digg |
|
« Previous day (Oct 18, 2006) | Main | Next day (Oct 20, 2006) »

Valid HTML! Valid CSS!

This is a personal weblog, I do not speak for my employer.