Hi Serge, [...]
> Do you have some more documentation and examples concerning > this mode of integration? Nothing besides the Javadocs. I recommend having a look at the SVN trunk or latest 1.1 snapshot to see the latest improvements to the Spring extension: http://www.restlet.org/downloads/1.1/current.zip > Currently today in Spring it is very simple to expose the > service layer using SOAP or Burlap for example. Interesting indeed, I wasn't precisely aware of these features: http://static.springframework.org/spring/docs/2.0.x/reference/remoting.html > Until Spring WS 2.0 is released it seems there is no easy way > to do this for REST. > CXF has REST support but it has such a dependency hell I do > not really consider it a usable solution. OK, there seems to be room for a Restlet solution :) > RESTlets look nice and I see some integration classes have > been provided > for Spring however I have not found a clear end-to-end > example of taking > a service defined as a bean in Spring and exposing it using RESTlets. There has been a lot of talks and propositions for solutions. The Spring extension in 1.1 makes a step forward as well. > Also as far as mapping requests to service is concerned it is > not clear how this can be done in an elegant fashion. > Could one imagine some annotations? REST has a resource-oriented approach that doesn't map directly to RPC or remote method invocation pattern (like RMI, Burlap, SOAP, etc.). Therefore you will need to expose your services as either Restlet's Resource subclasses (high level API) or a Restlet/Uniform instances (lower level API). > How are the HTTP verbs mapped to methods of the service? > Could this be done with annotations as well or conventions and reflection. There is a standardization effort related to annotations that we are part of (JSR-311), but the class-based approach provided by the Restlet's Resource class is very convenient IMO. I have entered a RFE for "Support Spring remoting" in Restlet: Best regards, Jerome
