Hi Dave, In general, you should pass the parent context to the constructor of your Restlet or Resource subclass.
Otherwise, in some cases, the setContext() is used for late setting of this context. I agree that it would be useful to propagate this call like for lifecycle method. I've taken note of this and will do it ASAP. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : David Fogel [mailto:carrotsa...@gmail.com] Envoyé : jeudi 19 mars 2009 05:08 À : discuss@restlet.tigris.org Objet : RE: Re: Why does the Restlet class have lifecycle methods? Hi Jerome- In addition to propagating start/stop life-cycle methods to any contained or "child" restlets, should restlets also, by contract, propagate any new Context they receive via setContext()? I'm not sure what the solution is, but I've been finding that I don't always have access to a Context at Restlet creation time, and then it becomes an issue when restlets contained within other restlets never get a Context set on them. Recommended practice? -Dave Fogel ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=13530 81 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1416229
