Unfortunately, we can't mix-and-match Spring MVC with JAX-RS in a satisfying model, because
1. JAX-RS annotations overlap with the Spring MVC annotations introduced in 2.5. This could result in duplicate request mappings, for instance.
2. JAX-RS is semantically different than Spring MVC, i.e. stateful vs. stateless
3. JAX-RS focusses on RESTful web services only, while Spring MVC focusses on web sites.
This does not rule out the possibility of using a JAX-RS as a backend to Spring MVC, something we are considering. Finally: we are also considering offering JAX-RS support in 3.0/3.1, in the same way we did for JAX-WS in Spring 2.5.