| Re: [jakartaee-platform-dev] VOTE: Specifications to add in Jakarta EE 9 |
Jersey also uses Activation btw, and EclipseLink JAXB, just to Mention two implementation Projects of other specs. Werner Sent from Mail for Windows 10 From: Kevin Sutter This is good, Markus. If there are still changes required in the JAXB API, then by all means this should be moved into the Jakarta realm. I was really questioning whether either of these two APIs need any further evolving. If you're saying that JAXB does, then that's good input.
There still are people out there who actively use JAXB and who even like to contribute new features to drive new releases of JAXB (me included).This is independent of the Jakarta EE platform actually, but it enforces a rename of the packages to "something-other-than-javax" still. As the projects are given to the EF, it simply comes in mind that treating them as if they would be parts of Jakarta EE might be the simplest solution. Certainly, any other package name would do, certainly. But the question is, who decides about these projects if they are not wanted to be parts of Jakarta EE? -Markus
Von:jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Kevin Sutter
Before I cast a vote, can I ask why these two APIs (XML Binding and Activation) need to move to Jakarta EE? Why can't we use the same argument as the SOAP API? Implementations can continue to use the javax versions of the XML Binding and Activation APIs, but they just will not evolve in the Jakarta EE space. Do we expect a need for these two APIs to continue to evolve? Or, maybe we have some dependencies on these APIs by other Jakarta specs that require these to be moved? I realize these were part of Bill's original proposal and there was much more discussion on the other APIs that we decided not to move. But, why did we decide that these two were required?
See previous email for context.
All committers please vote on this proposal for specifications to added from Java SE 8 to the Jakarta EE 9 platform specification.
The following APIs corresponding to Java SE 8 APIs will be added to Jakarta EE 9 Full Profile - Jakarta XML Binding - Jakarta Activation
Please vote by reply with +1, 0, -1 in accordance with the Eclipse Development Process.
Thanks
_______________________________________________ _______________________________________________ |
