If anyone wants to follow the conversation, the mailing is public and the archives are here: https://www.eclipse.org/lists/jakartaee-platform-dev/. There was some discussion about JAXB and JAXWS not being included in Jakarta EE 9, which was a concern for me as I see these as widely used and I feel that people would probably expect to see them in the platform. The option to include them in the platform but not move them to the jakarta namespace or evolve them was discussed. Where this gets complicated is that there are some changes planned for Activation, which would need to Activation to move the jakarta package and that has a knock-on effect for JAXB and JAXWS.
Backwards compatibility is interesting, we're also thinking about that on the TomEE side as we have the same challenge to solve there. Not sure we have the answer yet. At a high-level, I'm picturing using a javaagent to map things over to new package where old packages are being used, but I haven't tried anything yet. Thanks for the conversation here. Jon On Fri, Dec 6, 2019 at 3:49 PM Daniel Kulp <[email protected]> wrote: > > Interesting discussion… I'm honestly not sure how I feel about it. > > On one hand, it would be nice to be able to enhance the specs in the > future. On the other hand, there hasn’t been an enhancement or any plans > for an enhancement for several years. Thus, it could end up being a lot > of work and pain for nothing. > > I guess I would make JAX-WS depend on what decision is made for JAXB. If > JAXB changes, we’ll have to do a ton of work anyway. Thus, we might as > well do JAX-WS at the same time. > > The big trick will be getting the code to work with both the old > annotations and the new annotations. That might really require a lot of > work. I really don’t see how we could possibly drop support for the old > locations. They are used extensively in anything jax-ws and/or jaxb > related. Migration would potentially be a pain for everyone. > > Dan > > > > On Nov 26, 2019, at 3:49 PM, David Blevins <[email protected]> > wrote: > > > > There is a discussion and vote going on the Jakarta EE side of the fence > as to if the following APIs should be moved from javax into jakarta > namespaces. > > > > - JAXB (javax.xml.bind -> jakarta.xml.bind) > > - JAX-WS (javax.xml.ws -> jakarta.xml.ws) > > > > What "move" means is these APIs would be able to continue to evolve. If > they are not moved, they could still be supported but will be frozen > forever. At this time there is no intention of revisiting the topic in > future Jakarta EE versions and migrating things later; it's been explicitly > and widely voted down. > > > > So if JAXB and JAX-WS were to have a future in jakarta.xml.* that would > need to happen during Jakarta EE 9. > > > > As this is the project at Apache that implements JAX-WS: > > > > - Is there anyone who has ideas or desires to improve JAX-WS? > > - If they were migrated: > > - Would javax.xml -> jakarta.xml changes be welcome? > > - Are there people willing to help or do the work? > > > > Do people have any thoughts, questions or preferences? > > > > > > -- > > David Blevins > > http://twitter.com/dblevins > > http://www.tomitribe.com > > > > -- > Daniel Kulp > [email protected] <mailto:[email protected]> - http://dankulp.com/blog < > http://dankulp.com/blog> > Talend Community Coder - http://talend.com <http://coders.talend.com/> >
