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.