I blogged a little while ago about the proposed JSR 311, a REST API for Java. I’ve since tried to implement the annotations and processing described by the short example on Marc’s blog.
Now I’m not going to claim that what I’ve done is comprehensive or ‘production ready’, but it proves the point. The point it proves to me is that it’s possible to design small, simple APIs that dramatically simplify application programming (and is easily and cheaply implemented).
I’ve taken a quick look at Restlets and i’m impressed… but it’s a whole new application programming model. Does anyone really want that in JavaEE?
I’ll repeat myself. I think a simple API which can easily be added to JavaEE and which simplifes writing basic REST and HTTP/POX is a good approach. Lets let the more advanced bits be an area for innovation and competition for a little while longer.
Reminder: The contents of this blog reflect my personal opinions, not those of my employer.
Hi David,
Thanks for having a look at the Restlet project. Actually, I am part of the JSR expert group and plan on supporting the annotations on top of Restlets.
See some more details here:
http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/
Concerning JEE, the Restlet API was designed as an alternative to the Servlet API and to the HttpURLConnection class. Even though, it can easily work inside a Servlet container if needed or can reuse the HttpURLConnection class as one of the pluggable HTTP client connnectors. I don’t know yet if, one day, it will makes sense for the JCP to have it inside JEE. Maybe inside a new lighter set of APIs (ex: JWE for Java Web Edition)?
Best regards,
Jerome Louvel
—
http://www.restlet.org