All,
For a lot of people, there is still a lot of confusion about what it actually means 'included in the Jakarta EE 9 platform'.
When an implementation wants to be recognised as 'Jakarta EE 9 compatible', it needs to implement those specifications and pass the TCK.
If we remove some of the specifications present on Jakarta EE 8 platform, that will have only an impact on the 'certification' aspect. Because I'm pretty sure that all vendors which have now a Jakarta EE 8 compatible implementation will make sure that they don't break there existing customers by just removing JAXB.
So why are we removing specifications then? To make room for new innovations, the possibility for lighter runtimes, etc .... by not requiring specifications which are hardly used.
And yes, JAXB is still used a lot. But it is a special case since it was at Java SE level and used in many other specs, also rarely used. I think Kevin indicated quite well why it could be a problem to keep JAXB.
>So, if we move JAXB to the jakarta namespace, but not JAX-WS, then we will have two different JAXB APIs to support. But, we also recognize that JAX-WS is a legacy technology that probably shouldn't be part of the long term plans for Jakarta.
Regards
_______________________________________________ jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit