Re: [jakartaee-platform-dev] VOTE: Specifications to add in Jakarta EE 9

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

If JAX-WS is not in EE 9, and a product that implements EE 9 wants to also support JAX-WS, that that product would need to satisfy the dependency on JAXB.  It could provide both javax.xml.bind and jakarta.xml.bind APIs, or it could use one of the backwards compatibility approaches to map javax.axml.bind APIs to jakarta.xml.bind APIs.

But yes, having two implementations would make it hard to share binding classes.

Andy McCright wrote on 11/20/19 11:19 AM:

Would this also require adding the JAX-WS APIs to the EE9 spec?

The JAX-WS APIs that have been removed from the JDK currently have a dependency on JAXB.  If we evolve JAXB in EE9 (or just rename the packages), then we have some specs (like JAX-RS and maybe JPA, etc.) that depend on the jakarta.xml.bind.* packages while others (JAX-WS) that would depend on the javax.xml.bind.* packages. That would certainly make it difficult for EE9 applications to use both a JAX-RS and JAX-WS frontend that shares the same XML binding classes.

Thanks, Andy

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev