I’m one of those guys that thinks that REST is great technology. Sure, REST is does not do everything that SOAP can do, but I think that REST is built to be SIMPLE, something that SOAP and it’s WS-* buddies forgot about.
What we are missing is a good standard way to map REST to the simple POJO programming model that most of the Java industry has been quickly adopting. Seems SeXFire Dan has good start on a way of doing that!
Dan if you read this, I would make it even simpler if by default the method names for a service are determined by convention. For example, for a given XService, the methods:
getX(…) : is automatically mapped to a HttpMethod.GET
deleteX(…): is automatically mapped to a HttpMethod.DELETE
addX(…): is automatically mapped to HttpMethod.POST
updateX(…): is automatically mapped to a HttpMethod.PUT
deleteX(…): is automatically mapped to a HttpMethod.DELETE
addX(…): is automatically mapped to HttpMethod.POST
updateX(…): is automatically mapped to a HttpMethod.PUT