Since Spring 3 was released last December, I tested the new REST features in the MVC environment for a small commercial project involving the introduction of several RESTful web services that consume XML and return XML views using JiBX. I plan to use either Hibernate or JDBC Templates to save data.
As a Spring 2.0 developer, I found new Spring 3 (and 2.5) annotation features to do things completely paradigm-shift and personally found some of the new MVC annotation features that are hard to get speed for non-trivial applications - as such, I often have to dig information on forums and blogs, which is unclear how to get through the reference guide or from various Spring 3 REST examples on the Internet.
For end-to-end production quality and mission-critical applications that implement the RESTful architecture, I have to resist Spring 3 and, rather, use mature JSR 311 (JAX-RS) compatible with frameworks like RESTlet or Jersey for my code's REST layer (along with Spring 2 / 2.5 to tie things together)? I had no problems using RESTlet 1.x in a previous project, and it was pretty easy to speed up (without any magic tricks backstage), but when I started my current project, it first looked like a new REST element in Spring 3 MVC Framework would simplify a life.
Do any of you have any advice to give this? Does anyone know of any commercial / manufacturing projects using or successfully delivering new REST elements in the Spring 3 MVC Framework.
Many thanks
Glen