Hello... I just recently found this project and after evaluating decided to use it for a project that I am starting. Great project, I am very impressed so far. I am planning to run Restlet inside Jetty and Spring. Based on the Spring example for configuring all the restlets and URIs in the config, I am subclassing the ServerServlet so I can override the createApplication method so Spring can manage all the classes for me.
This works great except with defining Resources to handle the get, delete, put, post methods. Since the handler is now auto created and the Resource constructor requires a context, request, and response to be created it makes it difficult to use Spring to manage the Resource objects. If the idea is now that the Resource class is subclassed to provide the implementation, it generally is going to need other objects, like a DAO, to do the work. DAOs in particular are much simplified when using Spring and being able to inject them into the Resource is required if Spring is being used in my case. I can think of a possible work around by subclassing the object that creates Resources and making that object a Spring bean so I can properly inject other dependencies. It would be easiest if the the default constructor was still available and not deprecated, so that Spring could manage the Resources. Or possibly I should use explicit Handlers instead? I have not dug into Restlet enough yet to know which is the best way to proceed. Any ideas or comments would be appreciated. Thank you! -Brandon
