You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Bin Zhu <lu...@gmail.com> on 2014/03/26 09:25:17 UTC
ask for schedule for formal JAX-RS2.0 support
Hi,
I noticed from the following site that CXF 3.0 haven't claim formal JAX-RS
2.0 compliance yet, is there any rough schedule when will it be formal
supported? Thanks.
http://cxf.apache.org/docs/jax-rs.html
CXF 3.0.0 completely implements JAX-RS 2.0 including new Client API and has
been fully tested against the first JAX-RS 2.0 TCK which became available
to Apache (jaxrstck-2.0_26-Feb-2013).
Note: CXF 3.0.0 can not claim at the moment the formal JAX-RS 2.0
compliance due to the fact that the final JAX-RS 2.0 TCK has not been
available to Apache.
Re: ask for schedule for formal JAX-RS2.0 support
Posted by Sergey Beryozkin <sb...@gmail.com>.
I added a dedicated section:
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS#JAX-RS-JAX-RSCompliance
Sergey
On 26/03/14 10:40, Sergey Beryozkin wrote:
> Hi
> On 26/03/14 08:25, Bin Zhu wrote:
>> Hi,
>> I noticed from the following site that CXF 3.0 haven't claim formal
>> JAX-RS
>> 2.0 compliance yet, is there any rough schedule when will it be formal
>> supported? Thanks.
>>
>> http://cxf.apache.org/docs/jax-rs.html
>>
>> CXF 3.0.0 completely implements JAX-RS 2.0 including new Client API
>> and has
>> been fully tested against the first JAX-RS 2.0 TCK which became available
>> to Apache (jaxrstck-2.0_26-Feb-2013).
>>
>> Note: CXF 3.0.0 can not claim at the moment the formal JAX-RS 2.0
>> compliance due to the fact that the final JAX-RS 2.0 TCK has not been
>> available to Apache.
>>
> The formal compliance cam be claimed only if the implementation has
> passed the final TCK. Unfortunately Apache has lost the access to Oracle
> TCK and therefore we can not claim a formal compliance due to the fact
> we can't run Apache CXF against the final TCK.
>
> My personal point of view: CXF JAX-RS 2.0 implementation is technically
> sound with respect to supporting the 'letter' of JAX-RS 2.0. Testing
> against the Feb 2013 TCK has definitely helped too.
>
> The remaining known issue is:
> https://issues.apache.org/jira/browse/CXF-5650
>
> Of course, the final TCK may have the tests exposing some CXF issues.
> I'm hoping the users will help us to trace such issues if any in the
> absence of the final TCK package.
>
> Some EE-specific JAX-RS 2.0ptions (notably EJB) are not directly
> supported in CXF; Andriy Redko has done the initial CDI support which
> covers the relevant JAX-RS 2.0 text but it is a work in progress. I will
> be updating the wiki about it all too,
>
> I updated this page yesterday due to some external concerns about Apache
> CXF being not factually correct about it. I'm kind of impressed we've
> got the query on the dev list the next day :-).
>
> Cheers, Sergey
>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Re: ask for schedule for formal JAX-RS2.0 support
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
On 26/03/14 08:25, Bin Zhu wrote:
> Hi,
> I noticed from the following site that CXF 3.0 haven't claim formal JAX-RS
> 2.0 compliance yet, is there any rough schedule when will it be formal
> supported? Thanks.
>
> http://cxf.apache.org/docs/jax-rs.html
>
> CXF 3.0.0 completely implements JAX-RS 2.0 including new Client API and has
> been fully tested against the first JAX-RS 2.0 TCK which became available
> to Apache (jaxrstck-2.0_26-Feb-2013).
>
> Note: CXF 3.0.0 can not claim at the moment the formal JAX-RS 2.0
> compliance due to the fact that the final JAX-RS 2.0 TCK has not been
> available to Apache.
>
The formal compliance cam be claimed only if the implementation has
passed the final TCK. Unfortunately Apache has lost the access to Oracle
TCK and therefore we can not claim a formal compliance due to the fact
we can't run Apache CXF against the final TCK.
My personal point of view: CXF JAX-RS 2.0 implementation is technically
sound with respect to supporting the 'letter' of JAX-RS 2.0. Testing
against the Feb 2013 TCK has definitely helped too.
The remaining known issue is:
https://issues.apache.org/jira/browse/CXF-5650
Of course, the final TCK may have the tests exposing some CXF issues.
I'm hoping the users will help us to trace such issues if any in the
absence of the final TCK package.
Some EE-specific JAX-RS 2.0ptions (notably EJB) are not directly
supported in CXF; Andriy Redko has done the initial CDI support which
covers the relevant JAX-RS 2.0 text but it is a work in progress. I will
be updating the wiki about it all too,
I updated this page yesterday due to some external concerns about Apache
CXF being not factually correct about it. I'm kind of impressed we've
got the query on the dev list the next day :-).
Cheers, Sergey
Re: ask for schedule for formal JAX-RS2.0 support
Posted by Daniel Kulp <dk...@apache.org>.
On Mar 26, 2014, at 4:25 AM, Bin Zhu <lu...@gmail.com> wrote:
> Hi,
> I noticed from the following site that CXF 3.0 haven't claim formal JAX-RS
> 2.0 compliance yet, is there any rough schedule when will it be formal
> supported? Thanks.
To follow up on what Sergey has already stated…..
The agreement between Apache and Oracle/Sun that provided Apache with access to the various TCK’s expired a while ago. So far, attempts to setup a new agreement have not been successful due to Oracle requiring various restrictions that would be incompatible with the goals of the Apache foundation. Until Oracle is willing to adjust the terms, we’re not likely to have access again.
That said, there HAS been some attempts recently to get the conversation between Apache and Oracle restarted. We’ll see if that changes the situation at all, but we (CXF) would not be able to give a concrete timeline.
HOWEVER, the CXF community is more than willing to do whatever we need to do to make sure the CXF JAX-RS implementation is as complete and compatible as possible. If any users find any issues, they are encouraged to log the issues so they can be addressed.
Dan
>
> http://cxf.apache.org/docs/jax-rs.html
>
> CXF 3.0.0 completely implements JAX-RS 2.0 including new Client API and has
> been fully tested against the first JAX-RS 2.0 TCK which became available
> to Apache (jaxrstck-2.0_26-Feb-2013).
>
> Note: CXF 3.0.0 can not claim at the moment the formal JAX-RS 2.0
> compliance due to the fact that the final JAX-RS 2.0 TCK has not been
> available to Apache.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com