[jira] [Updated] (CXF-8053) Ensure JAX-RS usable features don't depend on jaxws

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (CXF-8053) Ensure JAX-RS usable features don't depend on jaxws

jagadeesh (Jira)

     [ https://issues.apache.org/jira/browse/CXF-8053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh updated CXF-8053:
-------------------------------------
    Fix Version/s: 3.3.3

> Ensure JAX-RS usable features don't depend on jaxws
> ---------------------------------------------------
>
>                 Key: CXF-8053
>                 URL: https://issues.apache.org/jira/browse/CXF-8053
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Priority: Major
>             Fix For: 3.3.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Follow up of https://lists.apache.org/thread.html/c68c4c73b4af274d2f0e162e8b5df62942d8cad41d829a9e2fa7a2f5@%3Cdev.cxf.apache.org%3E discussion.
> Idea is to not force JAXRS users to depend on jaxws in terms of dependency. Whereas it was acceptable for java <= 8, it is now impacting in java >= 9 since jaxws is no more part of the JRE.
> Proposal is to: drop the WebServiceFeature dependency in the AbstractFeature hierarchy by introducing a CxfBaseFeature keeping backward compatibility, provide native implementations of all feature and replace current implementations by plain delegation to the new one - to ensure existing users still have a functional setup. JAXRS users would use the new class and JAXWS ones can use the new one (probably preferred by javadoc) or the old one for compatibility.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)