Hi
At the moment I'm siding towards using JAX-RS via the CXF implementation
provided it is pretty stable.
If you look at the JAX-RS code you can see it's a pretty simple code and
there's a space for
a number of enhancements there. Jervis has already done a lot there, and the
ability to integrate JAX-RS services through Spring configuration with the core
CXF runtime is probably the most critical enhancement.
You can expect a better support for multiple formats coming in, perhaps we can
see some other features added for it to keep up with Jersey and indeed
outperform it in some areas.
In the end of the day it's quite a simple specification (JSR 311) so hopefully
if you find that some features you'd expect from the CXF implementation missing
then it would be simple to add a patch...
Cheers, Sergey
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.
--
View this message in context:
http://www.nabble.com/JAX-RS-maturity-tp15039120p15039120.html
Sent from the cxf-user mailing list archive at Nabble.com.
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
