ServerServlet is currently not designed to do this. In its nominal use case, there's nowhere for an existing Application instance to come from -- the ServerServlet is the actor responsible for instantiating all the Restlet plumbing from scratch. What I would do here (1.1) is to initialize ServerServlet with a custom Component subclass which provides the necessary hooks -- registering the Component with some context object or exposing a static to access a Component singleton, whatever works in your case. Then you can use these hooks to get access to the Component, and you can construct your own VirtualHosts and Applications. Or, as in our shop, you can put the needed intelligence directly into the custom Component to properly construct your VirtualHosts and Applications.
On Sat, May 24, 2008 at 4:32 AM, Hendy Irawan <[EMAIL PROTECTED]> wrote: > I guess it boils down to the question: > > How do I properly specify a Restlet Application *object* (instead of > classname) to a Restlet Servlet object?
