Hi Yuri, I see your point now. In fact, we also plan to support WAR deployment in standalone mode too for version 1.1. It will be an hybrid WAR packaging but it would be possible to create a WAR file that is both deployable in a Servlet container or in a standalone Restlet component.
As a consequence, as a Restlet component can contain several applications, it must handle several WAR client instances at the same time, hence the need for a special dispatching as those WAR clients can't be shared between apps. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Yuri de Wit > Envoyé : samedi 5 mai 2007 00:26 > À : [email protected] > Objet : Re: Example of a Restlet Application/Servlet using > both Client and Server > > Jerome Louvel <contact <at> noelios.com> writes: > > The WAR client is special in the sense that is allows access to data > > 'relative' to the current application using it (via a dispatcher). > > Therefore, it needs to know where the WAR file is located > or where it was > > unpacked. This is specific for each app and can be shared with other > > co-hosted apps. > > Hi Jerome, > > Its not that important, just an fyi. > > My only point was that the WAR client exists specifically for > WAR deployments > but the code that deals with it exists in the core framework > which is used by > both WAR and standalone deployments. > > I was just wondering if the WAR client shouldnt be added to > the Component by the > ServerServlet (WAR deployment only) instead of an "if" > statement in the > ApplicationDispatcher. To my knowledge the WAR Client is a > client like any other > and should be dispatched in the same way (or am I missing something?). > > thanks, > > -- yuri
