BEA and Oracle incorporate Sun's Project Tango

Hi There,

How about spring web services>/a> ?

Thank you,

BR,
~A

Your article says that Project Tango sometimes does not support specs that are becoming standards. That is not accurate. Project Tango implements both standard and spec submissions (still needing finalization). See the page Project Tango Specs. These are the same specifications implemented by .NET 3.0 as shipped in Vista.

Harold, the statement in the article is correct. If you follow the link you'll see that it refers to WS-Transaction, which Tango supports but the version is not what has become the standard. If you see, I had a conversation with Ryan Shoemaker where he said that Tango supports the 2004 version of WS-C/WS-AT. Although several other vendors do as well, the major players in that space already support WS-TX 1.0 and often 1.1 as well. I could be wrong, but by implication Tango also doesn't support the 2006 version of WS-A either, since the 2004 version of WS-Transaction is dependent on the 2004 version of WS-A. I'd certainly be interested in knowing if that assumption was wrong.

Hello Mark. The main goal of Tango is MS .NET 3.0 interop. So Tango implements the same set of specifications as .NET 3.0 in Vista. I imagine that future versions of .NET will update to standard specifications (instead of the submission versions that were available when .NET FCSed). We will likewise do updates. My main point is, the article implies Tango is misaligned on specifications, but, as I pointed out, we are perfectly aligned with our target: .NET 3.0

Mark, To add to Harold's comment - Tango does support both Member Submission and W3C Core and SOAP WS-Addressing. The WSDL Binding spec is no longer valid and Metadata will be supported when it goes final.

Thanks Harold and Arun for the update. For my own edification, does Tango's support of W3C WS-A run in parallel to the 2004 version that is needed by WS-Transaction?

hi,

the article seems to imply that webservice stacks are becoming a commodity. however, to me it seems that this is far from the truth (yet). basic SOAP/WSDL support is really not the issue - but the (IMHO) desparately needed industrial-grade support of WSDL 2.0, WS-A, WS-RM, WS-Security and other WS-* specs that "just works" is almost ridiculously elusive in Java-land.

also, in contrast to what the article seems to suggest, it is my impression that project Tango (WSIT) is really one of very few implementations of these "advanced" WS-* specs that is at least on track to deliver.

i'd be very interested to be corrected on this - but my perception of the current state of "advanced" webservice stacks is roughly as follows:
- AXIS1: widely deployed but only basic WS-* support and in maintenance mode as focus has shifted to AXIS2
- AXIS2: addresses all important WS-* specs and well underway to implement them; not too much uptage in many tools yet (such as ESBs (apart from Synapse))
- WSIT/Tango: ditto
- XFire: widely deployed but only basic WS-* support and essentially superceded by Apache CXF
- Apache CXF: under heavy development but major "advanced" WS-* specs seem to be supported today
- JBossWS: no support for "advanced" WS-* specs that i can see

so much for commoditisation - i would be a happier person if i could (today) pick any mature, reliable webservice stack that implements advanced WS-* specs and interoperates flawlessly with at least .Net...

(and, while we are at it, where is the standardisation of the APIs beyond JAX-WS 2.0 and basic SOAP/WSDL??)

sorry for the negative vibrations ;-)
gerald

www.gerald-loeffler.net

Web Services stacks (or more correctly SOAP stacks) are becoming a commodity. Axis1 did that very well. Back in the early days of Web Services, everyone had their own stack implementation. That's no longer the case. If the original article is correct and BEA and Oracle have adopted Tango, then this is a significant step towards commoditization, at least as far as Tango is concerned.

But you're right, there is a difference between the basic support for Web Services (all you need there is a good standards compliant SOAP stack) and the more advanced capabilities. The former is pretty easy to achieve, whereas the latter requires a lot of time and effort (not least of which is participating in all of the standards interoperability workshops).

As for standardising the APIs, well for Java you have to look at the JCP for that. It's often a slow process unfortunately.

Yes, both versions are supported parallely.

I'd like to post a correction to the article.

BEA WebLogic 10 is using only JAX-WS and Oracle is not using any part of either JAX-WS/Tango. BTW, the new aggregated stack is called Metro (blogs.sun.com/arungupta/entry/announcing_metro_...).

Just to add though Metro is now supported in JBoss as well. And we certainly hope BEA and Oracle picks up Metro :)