JSR-311 considered complete and utter crap
JSR 311: JAX-RS: The JavaTM API for RESTful Web Services
http://jcp.org/en/jsr/detail?id=311
Point 1:
``2.6 Why isn't this need met by existing specifications?
The APIs currently available for the development of RESTful services are too low-level and require a deep understanding of HTTP issues and design patterns. We need to enable developers to write these services easily.''
If you don't have a deep, low-level understanding of HTTP issues and design patterns then you're unlikely to be able to develop truly RESTful services. This is just another attempt at dumbing down technology to make it more accessible to unskilled practitioners.
Point 2:
``The goal of this JSR is to provide an easy to use, declarative style of programming using annotations for developers to write REST ful Web Services and also enable low level access in cases where needed by the application.''
This means the framework will attempt to make it natural for you to build RESTful services but you're free to completely mangle your implementation because of your incomplete understanding of REST and HTTP principles.
And finally:
``RESTful Web Services is a relatively new area in the industry and there are still a lot of unknowns in this space. For example, a key aspect of RESTful Web Services is for the service to be stateless. However, this often requires the developer to produce boiler-plate state restoration code that could be avoided with state-aware API help.''
Since one of the fundamental principles of REST architecture is Hypermedia As The Engine Of Application State this makes me wonder whether the authors of this JSR even understand REST principles themselves.
http://jcp.org/en/jsr/detail?id=311
Point 1:
``2.6 Why isn't this need met by existing specifications?
The APIs currently available for the development of RESTful services are too low-level and require a deep understanding of HTTP issues and design patterns. We need to enable developers to write these services easily.''
If you don't have a deep, low-level understanding of HTTP issues and design patterns then you're unlikely to be able to develop truly RESTful services. This is just another attempt at dumbing down technology to make it more accessible to unskilled practitioners.
Point 2:
``The goal of this JSR is to provide an easy to use, declarative style of programming using annotations for developers to write REST ful Web Services and also enable low level access in cases where needed by the application.''
This means the framework will attempt to make it natural for you to build RESTful services but you're free to completely mangle your implementation because of your incomplete understanding of REST and HTTP principles.
And finally:
``RESTful Web Services is a relatively new area in the industry and there are still a lot of unknowns in this space. For example, a key aspect of RESTful Web Services is for the service to be stateless. However, this often requires the developer to produce boiler-plate state restoration code that could be avoided with state-aware API help.''
Since one of the fundamental principles of REST architecture is Hypermedia As The Engine Of Application State this makes me wonder whether the authors of this JSR even understand REST principles themselves.