Hi
On 12/07/13 09:14, alex wrote:
Hi,
I am a CXF user on jax-rs, recently I find out the CXF has supported some
features of jax-rs 2.0, it is really great news to us.
But compared with jax-rs 2.0 spec, it seems some important features, such as
standard client API, validators, are still not supported. Like asychronized
invocation, I am not sure it is the same with spec defined? or cxf own defined?
I wondering will CXF fully support jax-rs 2.0? When or which release should it
be done?
Yes. CXF will fully support JAX-RS 2.0, except for some EE-specific
extensions which is where I believe TomEE is/will be helping.
Let me provide a short overview of where we are now with respect to
completing JAX-RS 2.0:
1. All of JAX-RS 2.0 standard server-related features have been
implemented and TCK validated against the early 2.0 TCK - the latest TCK
will have more tests but overall the compliance is high-level.
Server side async processing is completely supported too FYI.
What is not supported just yet:
- Injection of Configuration interface - trivial to fix
- Bean Validation: it is actually an EE feature but as I mentioned
earlier IMHO we should have it done in CXF too, and actually consider it
done such that it works for all of CXF frontends
2. Client
Most/all of Client API will be done for CXF 3.0 due end of this year.
CXF JAX-RS already supports all of client-side 2.0
filters/interceptors/exceptions/Response enhancements and already offers
2.0 AsyncInvoker support (via WebClient.async() link).
We are quite close there, what remains is completing support for
SyncInvoker, and all of client-side boostrapping, etc...
Sergey
