spring mvs vs jax-rs rest
jax-rs, spring-mvc
Solution
JAX-RS pros:
- JSR standard
- Can be run without servlet container (grizzly, simple, ...)
- Production-ready implementations (jersey, cxf, resteasy, restlet, ...)
- designed for REST applications only
Spring MVC pros:
- Provide "full" stack, not just REST facilities
- Dependency injection / AOP / Transactions
- Pluggable view templates (JSP, freemarker, velocity, ...)
I've never noticed performances bottlenecks with one or other, except spring application take a longer time to deploy and warm-up.
Problem
Any reason why i should choose jax-rs (jersey ) instead of Spring-mvc for rest implementation. Spring comes with additional features in addition to rest like aop , security , ioc etc. . You get all you need form spring. Any performance/features drawbacks choosing spring (i suspect that ).