Upgrade to JAX-RS 1.0

[Sergey Beryozkin <se...@progress.com>]

Hi,

I've just updated a jax-rs frontend in 2.2-SNAPSHOT trunk to support JAX-RS 1.0 [1].

The following main changes in 1.0 (some of them came from 0.9) will affect CXF JAX-RS 0.8 users :

1. ProduceMime and ConsumeMime annotations have been renamed to Produces and Consumes
This is likely to affect any CXF JAX-RS user.

2. MessageBodyReader and MessageBodyWriter signatures have changed. 
Those who wrote custom body readers/writers will need to recompile the code but the implementation won't need to be changed

3. HttpHeaders.getLanguage() and getAcceptableLanguages() return Locale and List<Locale> respectively


>From now on, we'll focus on making sure CXFJAX-RS fully implements 1.0. As far as I can see, this will require us to
1. Complete the (partial) implementation of UriBuilder which can be a handy utility when building complex URIs - at the moment there're a number of ways to do what UriBuilder can but it requires a better knowledge of how URI are structured...
2. Finish UriInfo implementation - it's mostly complete but the newly introduced 3 methods
3. Support newly introduced GenericEntity (which can wrap and preserve collections's type info)
4. Support newly introduced FormParam
5. Add support for javax.activation classes such that people can do multipart related updates
6. Work on current issues and add more system tests

That's the basic plan, as far as the goal of completeing JAX-RS work and doing TCK is concerned.
In parallel, we'll start thinking on how to make CXF JAX-RS stand on its own, and how to do advanced JAX-RS/JAX-WS services.

It's likely to take a bit of time to achive all these goals given that the resources are limited so to say :-)
In meantime - please give a try - the feedback is most welcome,  don't worry if you feel you know there're better JAX-RS implementations out there :-) - it's up to you the users to choose and we understand it, and have fun :-) ! 

Cheers, Sergey

[1] https://jsr311.dev.java.net/nonav/releases/1.0/index.html

JAX-RS 1.0 and CXF 2.1.x

[Sergey Beryozkin <se...@progress.com>]

Hi,

Now that 2.2-SNAPSHOT trunk has been updated with JAX-RS 1.0 api, the question is whether these updates
can be back-merged to 2.1.x branch for users of the next to be released CXF-2.1.4 to start playing with the final JAX-RS 1.0.

Given that for JAX-RS 0.8 users it's obvious the breaking changes will happen and are expected, when they move to 1.0, one option is 
to do an immediate merge to 2.1.x-fixes and let the users to update their code asap and forget about the necessity to upgrade their 
code at some time later on. CXF 2.2 is still not quite there and 2.1.x users wishing to do the latest JAX-RS might not be willing to 
switch to 2.2.

Another option takes into consideration the fact that some 2.1.3 users have some production code and they'd like to awail of any 
fixes (addressing some of the problems lurking in both 2.2-SNAPSHOT and 2.1.x) which might've been back-merged into 2.1.x, so they'd 
like to pick them up in 2.1.4 without changing the code. In this case we can either backmerge JAX-RS 1.0 updates either to a later 
2.1.5

Next option is to  JAX-RS 1.0 updates away from 2.1.x

I'd go for either 1 or 2, but it's up to the users to decide. if anyone is concerned about option 1, then let us know please

Thanks, Sergey