What happened to JAX-WS 2.1 & JAX-B 2.1?
Update: In my dismay I was getting the JCP & W3C processes all mixed up - duh. It seems it was the W3C WSDL Binding specification that fell at the last hurdle, presumably causing the JAXB 2.1 and JAX-WS 2.1 specifications to be withdrawn.
Update2: Vivek Pandey’s Blog post seems to confirm the above. I’m all for blogging to get the word out to the masses but the JCP Expert Group(s) should update their official JSR pages too. Regardless, the fact that JAX-WS 2.1 JAXB 2.1 was finalized on a Candidate Recommendation W3C specification reflects poorly on the quality of specification that the JCP is producing.
Does anyone know what happened to JAX-B 2.1? JAX-WS 2.1 (JSR-224) was released a few weeks ago, but the JCP have since pulled the specification, reference implementation and TCK. The reason given is that the W3C WSDL Binding specifiication, referenced by the JAX-WS 2.1 JAXB 2.1 specification announced back in December, did not make it past the Candidate Recommendation stage and apparently needs to be replaced with an alternative specification.
Does anyone have any pointers on why this happened (and what the old JAX-WS 2.1 candidate might be replaced by or when)?
Update 3: Looks like WS-Addressing WSDL Binding is being replaced by WS-Addressing Metadata.
3 Comments to What happened to JAX-WS 2.1 & JAX-B 2.1?
Leave a comment
What I'm Doing...
- Weird, Jeff Stelling (brilliant Sky Sports 'Gillette Soccer Saturday' anchor) is to be the new Countdown host. He might be good... 4 hrs ago
- Merging Irish banks until only BOI & AIB exist is terrible idea. Their assets are too expensive to be 'saved' if required(>100% of I ... 8 hrs ago
- I've got a ticket for the Pumas game tomorrow...can't wait! 11 hrs ago
- @donncha OO now has a native OS X build of v3. Latest neooffice is still cut from OO v2 source still I think so it's probably a bit behind. 11 hrs ago
- @EvertB Wondering if anyone 'in the know' could comment on status of irish mobile operator network capacity? 18 hrs ago
- More updates...
Posting tweet...
Blogroll
LinkRoll
Category Cloud
amazon api app apple atom atompub australia banks beacon berlin blogging blosxom capeclear content copyright data dev drm dublin eclipse economy facebook firefox food football fowa future games google hardware identity internet ireland irish java junk linux mac media microsoft mobile movies music n800 net nooked oauth openid opensocial opml osgi oss patents politics polls process rails railsconf rest rss ruby search soa social software spam sport tech travel trip tv uk us vodafone wayoutthere web2.0 web services why xml yahoo youtube
Recent Posts
Recent Comments
- d harris on How many James Bond films are there?
- rud0y on How many James Bond films are there?
- Fergus Burns on Moving On
Archives
Photos
|
Nothing happened to JAXB 2.1. The spec and the RI are available as usual, and it has never referenced W3C WSDL Binding to begin with.
I think you are mixing up JAXB and JAX-WS.
The JCP’s JAXB homepage (http://jcp.org/en/jsr/detail?id=222) still contains no reference to JAXB 2.1. I appreciate that the JAXB R.I. project page (https://jaxb.dev.java.net/) does but that isn’t the ‘home’ of the spec.
That said, I was indeed referencing JAXB incorrectly in my post, I have updated to correct.
In JCP terminology, “JAXB 2.1″ corresponds to the maintenance release 1 of JSR-222. So the “maintenance release” that started on Dec 14th 2006 is the JAXB 2.1 release.
JCP website is full of JCP jargons like this, so there’s little wonder people get confused about this. I’d like to think JAXB java.net page does a better job of using terms that people understand.
Hope this clears your confusion.