Hello Daniele > Now, I am reading the tutorial and I see that while in the get started there > is > a "servlet approach" (I have a web.xml and configure a RestletServlet to be > loaded and the arrives the restlet application subclass...) In the "first steps" page, there is also the standalone approach. http://www.restlet.org/documentation/1.1/firstSteps#part04
> If I have well understood, restlet is also an alternative to servlet model > so I > do not need to, say, include servlet.jar in classpath cause there are enough > stuff to handle communication between component in restlet itself. Finally, > servlet package is just an "integration" package, but I do not really need > it so > is better to follow the "clean" restlet way and start a server. You're right, you can see the servlet extension as an integration of the Servlet world into the Restlet word (or vice versa). Actually, this is also the opportunity to choose the approach you're more comfortable with. If you need to work with Servlets, that's fine; you can still learn working with Restlet by following the tutorial. Otherwise, start from scratch with a "clean" classpath. best regards, Thierry Boileau
