Well, the first thing to remeber is that JSR311/JAX-RS is, itself, an evolving spec. It hasn't reached anything close to "final" yet (they are at 0.5) so some changes are definitely to be expected. Also, because it's not close to final yet, there really isn't a TCK for it or anything that we can test against to guarantee compatibility.
On of the goals of adding JAX-RS stuff to CXF was to have a good implementation as the spec evolves so when it is final, we can be "right there" and provide an implementation. So, to answer your question about "Will there be a lot of changes in the near future?" I don't really know. The spec could be completely redone in 0.6 or something. We don't really have full control over that. Do I expect that level of change, no, but it is possible. What we have in the 2.1 trunk of CXF is definitely a good starting point. A lot of things are working fairly well. There are a couple areas where jersey does things that we don't support yet, but that gap is slowly closing. However, there are other things that you can do with CXF that is harder (or cannot) to do with Jersey. Dan On Wednesday 23 January 2008, brmaguir wrote: > Hi, > > I'm currently deciding on a REST framework to use for an upcoming > project and have been looking at a number of possibilities including > CXF. > > Just a few quick questions. How mature is the JAX-RS implementation? > Will there be a lot of changes in the near future? Have any of you had > experience with the Jersey implementation of the JSR311 standard, and > if so how does it compare to the CXF implementation? > > At the moment I'm siding towards using JAX-RS via the CXF > implementation provided it is pretty stable. > > Cheers. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
