[jira] [Resolved] (CXF-5785) JAX-RS XML Schemas at CXF site need to support multiple CXF versions

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

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

Sergey Beryozkin resolved CXF-5785.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1
         Assignee: Sergey Beryozkin

The conversion code between 2.x and 3.0 client elements works in Spring,   done for Blueprint, pending the validation. I will reopen this issue for 3.0.2 if proves necessary

> JAX-RS XML Schemas at CXF site need to support multiple CXF versions
> --------------------------------------------------------------------
>
>                 Key: CXF-5785
>                 URL: https://issues.apache.org/jira/browse/CXF-5785
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>             Fix For: 3.0.1
>
>         Attachments: patch.txt
>
>
> in CXF 3.0.0 jaxrs:client moved to a new namespace and a new schema document. The latest jaxrs.xsd without jaxrs:client got uploaded to the site.
> Side-effect: CXF 2.x clients using jaxrs:client see the validation issues.
> At the moment the workaround is to keep the old jaxrs:client definitions inside new jaxrs.xsd.
> Possible longer-term solutions:
> 1. introduce jaxrs2x.xsd schema and advice CXF 2.x clients to start referencing jaxrs2x.xsd
> 2. introduce jaxrs3x.xsd, upgrade CXF 3.0.1 jaxrs,xsd to reference jaxrs3x namespace - we would need to keep the numbering or dates added from now on
> 3. have somehow jaxrs;client residing in rs-client module use the same target namespace as before, effectively reverting a namespace change
> Preferred options: 1 or 3
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)