Hi Thierry, This is Nexus, so: restlet version 1.1.1, integrated with Plexus (latest beta2) and Jetty as servlet container. But, the Application itself runs in slightly modified SerlvetServer (modified, since it does a lookup for Application as Component, and does not instantiates the Application manually, but falls back to "default" SerlvetServer behavior if component is not found.
Is there any "critical" place (ie. ServletServer Application instantiation, or whatever) what could affect the RootRef calculation? Will look at your example, and will try to find where are we messing it within Nexus. ~t~ On Wed, Nov 12, 2008 at 11:10 AM, Thierry Boileau <[EMAIL PROTECTED]> wrote: > Hello Tamás > > it seems weird. Could precise your version of Restlet? Are you working with > the Spring extension? > I send you a sample Eclipse project which seems to work fine (Restlet 1.1). > It displays the rootRef from a resource. > > > Best regards, > Thierry Boileau > -- > Restlet ~ Core developer ~ http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > > Hi there, > > i just want to ask is it valid to have > > request.getRootRef() > > returning null? > > That is happening when Application is "mounted" at root of the j2ee > webapp container (at "/"). When it runs in some of the "usual" context > paths (ie. "/nexus"), it works fine, and returns the expected > reference to the root of that context path. > -- Thanks, ~t~
