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
