I don’t think there are many of them. To a large extent, this is a religious argument and the “easy-to-integrate into my stack” argument of the CXF, I find it compatible with JAX-RS, like RESTEasy, and - personally - I think it should be your biggest driver. You should strive to develop for JAX-RS, and then assume that you can swap different implementations if necessary. Other factors to consider:
- serialization (e.g. using Jackson formatting for JSON), both for performance and overall flexibility
- client standardization - there is currently no standard JAX-RS client standard, but this is the space I would look for, since it would be nice to have the same guarantees for the client code that JAX-RS provides the server code
source
share