Hello: I'm new here, and I'm evaluating Restlet to use in a solution we are going to implement. To cut a long story short, here's a description what I'm up to.
For 2 or 3 weeks we're going to focus on a HTTP implement with Resources (servlets or restlets) as the entry point of each service, each Resource will be responsible for managing 3 queues (in, out, err), probably JMS queues, and software component(s) (maybe using a facade) conditionally consuming the inQ. Next, we'll try to implement some kind of "connector" for user agents that uses mail, probably using some kind of command pattern so that original messages (HTTP, mail, etc...) will be "translated" to one single "type" before arriving to the queues. We'll probably be using Spring DataBinder for that, and then SpringIntegration between the Queues and the sw component(s). After that, same thing to some other kind of connectors, like FTP and maybe others. I'm trying to evaluate if Restlets are a good fit for this structure, instead of plain-old servlets. My boss doesn't want to use Restlets because practically it will only handle the request and we can do that with servlets so no need for another dependency. So, for instance, can I do the "translation" I was talking about with Restlet instead of servlet + spring DataBinders? Is there some special way to manage queues? logging? monitoring? What's the level of integration of Restlet with SpringIntegration (and/or Cammel), if any? And while i'm at it, and with OSGi? What's the relation between Restlets and JSR-311? Are the Restlet team committed to conform to it? Thanks all for your assistance.
