cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin" <sbery...@progress.com>
Subject Re: JAXRS : moving to JAX-RS 1.1 api
Date Tue, 29 Sep 2009 16:26:38 GMT
I meant to send this message earlier on.

I've updated the 2.3-SNAPSHOT (trunk only) to depend on the jax-rs api 1.1 two weeks ago.
I'll create JIRA subtasks later on, but
the 3 JAX-RS requirements have already been implemented earlier on (sorting of message body
providers by type, support for a
'fromString' method plus new Request method). Should have it all supported in time for 2.3
(not sure about the optional EJB
requirement though - will welcome contributions). More updartes to come later on.

If you're playing with multi-bundle DOSGI distributions and replacing a shipped 2.2.3 bundle
with 2.3-SNAPSHOT then please make sure

http://repository.apache.org/snapshots/org/apache/servicemix/specs/org.apache.servicemix.specs.jsr311-api-1.1/1.4-SNAPSHOT/

is installed instead of org.apache.servicemix.specs.jsr311-api-1.0

A corresponding Maven dependency is here :

<dependency>
    <groupId>org.apache.servicemix.specs</groupId>
    <artifactId>org.apache.servicemix.specs.jsr311-api-1.1</artifactId>
    <version>1.4-SNAPSHOT</version>
</dependency>


Sergey


> Hi,
>
> Now that we have CXF JAX-RS passing TCK for jax-rs 1.0 api, it's time to start thinking
about updating the jax-rs api dependency
> to 1.1.
>
> The following changes might affect existing users :
>
> 1. javax.ws.rs.core.Response.Status.Family class
>
> has been removed and instead
>
> javax.ws.rs.core.Response.StatusType & javax.ws.rs.core.Response.StatusType.Family
>
> have been added
>
> 2. As a result of 1,
>
> - public static javax.ws.rs.core.Response.ResponseBuilder javax.ws.rs.core.Response.status(javax.ws.rs.core.Response.Status)
> - public javax.ws.rs.core.Response.ResponseBuilder
> javax.ws.rs.core.Response.ResponseBuilder.status(javax.ws.rs.core.Response.Status)
> - public final javax.ws.rs.core.Response.Status.Family javax.ws.rs.core.Response.Status.getFamily()
>
> have been removed and instead
>
> - public static javax.ws.rs.core.Response.ResponseBuilder javax.ws.rs.core.Response.status(javax.ws.rs.core.Response.StatusType)
> - public javax.ws.rs.core.Response.ResponseBuilder
> javax.ws.rs.core.Response$ResponseBuilder.status(javax.ws.rs.core.Response.StatusType)
> - public final java.lang.String javax.ws.rs.core.Response.Status.getReasonPhrase()
> - public final javax.ws.rs.core.Response.StatusType.Family javax.ws.rs.core.Response.Status.getFamily()
> have been added.
> 3. new method
>
> javax.ws.rs.core.Response$ResponseBuilder javax.ws.rs.core.Request.evaluatePreconditions()
has been added to Request interface
>
>
> So in summary: if you haven't used javax.ws.rs.core.Response.Status.Family or Response.status(Response.Status)
or
> ResponseBuilder.status(Response.Status) then your application code won't be affected.
> If you have used Request helper befor then you'd only need to recompile but not change
the code.
>
> Let me know please, by replying to this thread or pinging me on #cxf or directly if the
above changes will affect you. If no users
> will have their (production) code affected then I see no reasons in postponing the move
to jax-rs 1.1 api
>
> Thanks, Sergey
>
> [1] https://jsr311.dev.java.net/drafts/changelog.1.1.html


Mime
View raw message