Hi guys, Very reasonable indeed. I've fixed the behavior in SVN branch 1.1 and in SVN trunk (with additional refactoring in the engine).
Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Thierry Boileau [mailto:[email protected]] Envoyé : jeudi 11 décembre 2008 17:30 À : [email protected] Objet : Re: ApplicationStatusFilter - bug ??? Hello Rémi, your suggestion looks really reasonnable. As I'm not fully aware of the original design choice, I've entered an RFC => http://restlet.tigris.org/issues/show_bug.cgi?id=683 Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com > Hello, > > I just wonder if it is a bug having in ApplicationStatusFilter : > public ApplicationStatusFilter(Application application) { > super(application.getContext(), application.getStatusService() > > .isOverwrite(), application.getStatusService() > .getContactEmail(), "/"); > } > instead of something like that : > > public ApplicationStatusFilter(Application application) { > super(application.getContext(), application.getStatusService() > .isOverwrite(), application.getStatusService() > > .getContactEmail(), > application.getStatusService().getHomeRef().getTargetRef().toString()); > } > Because that way doing this on Application initialization has no effect: > > getStatusService().setHomeRef(new Reference("/some/path/")); > > Cheers, > Rémi ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=982916 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=990973
