Was not thinking to drop it from the parent but more to get soap free flavors of cxf features which would then be usable in jaxrs apps without any issue. In other words we would get a cxf.AbstractCxfFeature used as base for all impl and current existing ones would be deprecated and would delegate to the new ones. No backward compat issue I think.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 31 mai 2019 à 16:49, Daniel Kulp <[email protected]> a écrit : > > > > I just realized LoggingFeature depends on javax.xml.ws.WebServiceFeature > > > > Is it possible to drop that dependency in the target to run on java ~11 > > without javax.xml.ws dependencies? > > Certainly not without breaking compatibility and everyone using any of the > CXF provided features. AbstractFeature (in core) subclasses > WebServiceFeature so that any of the features can be added directly to any > of the jax-ws endpoints/clients directly and everyone using them does so. > Thus, removing that as a parent would completely break everyone. > > > -- > 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/> >
