It depends on what you are trying to build with Restlet. If you need something that a JEE container provides (e.g. lifecycle services, deploy/undeploy applications, integration with existing Servlet code), or are required to run in an existing JEE container for business reasons, then you should use the ServerServlet approach.
If you don't need any of the JEE container features and aren't using any Servlet API, it is good to have the ability to run Restlet in standalone mode (start Component from "main") with your choice of connector. This is excellent for lightweight embedded systems, and also for any "legacy-free" new application which is designed totally around Restlet and doesn't need any JEE baggage. There is also at least one other really interesting option, which is to run Restlet as an OSGi service within an OSGi framework. This shares some properties/advantages of both the JEE and Standalone approach, and introduces other neat possibilities. Some of us (at least Hendy and I that I know of) have played with Restlet on OSGi a lot. - Rob On Fri, Nov 14, 2008 at 8:47 AM, Gan123 <[EMAIL PROTECTED]> wrote: > > Hi, > > i am new to restlet, started exploring. i found we can access an > application mapped to ServerServlet in a web application, as well we can > create a application where we use restlet client to create a client and use > main to start application. > > in the first approach we are using the web server, where as the second > approach we use restlet webcontainer for our application launch.. am i > right? > > if not clarify me, as tell me which way is suggested and best > > Thanks in advance > -- > View this message in context: > http://n2.nabble.com/which-is-better-way-for-web-application-using-RESTlet--tp1498498p1498498.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > >
