It is an acknowledgement that although the spec is largely a legacy spec, there are changes that are needed to facilitate usage of the spec going forward, but it should not be required. The reality is that our customers using JSR-109 will not want to modify their code to run under our EE 9 container, so it is mostly about enabling a porting layer to deal with only one JAXB implementation + whatever other changes are needed to support the backwards compatibility use case.
How is "optional" different from "not added"?What can I do with an optional spec vs. a spec that exists but is not included in Jakarta EE?Steve Millidge (Payara) wrote on 11/22/19 10:36 AM:
Perhaps we need to kick off a vote on JAX-WS, it could be optional? Adding it as optional will still mean the project will have to do a release so will likely impact timelines. Scott,This is exactly what we're struggling with in our discussions at IBM. We have many existing JAX-WS customers. 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.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom: Scott Stark <starksm64@xxxxxxxxx>To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>Date: 11/21/2019 03:04Subject: [EXTERNAL] Re: [jakartaee-platform-dev] VOTE: Specifications to add in Jakarta EE 9Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
There still could be an update of JAX-WS to match the JAXB package changes without JAX-WS being an official part of EE 9 I suppose. JAX-WS is certainly a legacy tech that I would not expect customers to want to have to update their use for JAXB changes, but it could be beneficial to porting layers to have a JAX-WS release that allows for a runtime to make use of a single EE 9 based JAXB implementation.
|
