Hi again, I've done some tests and Context.getCurrent() works for me (SVN trunk). It is possible that we have fixed this since 1.1 M5 as we add a couple of context bugs.
If you could try again with a recent snapshot that would we great. Otherwise, we'll follow this when 1.1 RC1 is released next Wednesday. 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 : Jerome Louvel [mailto:[EMAIL PROTECTED] Envoye : lundi 18 aout 2008 16:06 A : [email protected] Objet : RE: Guice and 1.1m5 Hi Chris, I've entered a report for this: "Context.getCurrent() doesn't seem to work" http://restlet.tigris.org/issues/show_bug.cgi?id=568 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 : news [mailto:[EMAIL PROTECTED] De la part de Chris Lee Envoye : jeudi 14 aout 2008 16:40 A : [email protected] Objet : Re: Guice and 1.1m5 Tim Peierls <tim <at> peierls.net> writes: > > In which case the fix for Chris might be as simple as providing a Context instance to the Application.I still think it would be worth "future-proofing" FinderFactoryModule, though.--timOn Thu, Aug 14, 2008 at 4:05 AM, Jonathan Hall <jonrhall <at> gmail.com> wrote: You would think, but I already was. I'm not positive that Context.getCurrent() actually works as expected, but the documentation does say to only use it as a last resort, and I don't understand everything well enough to actually make that claim. Anyway, Application.getCurrent().getContext() seems to work, so hopefully that will take care of it. Thanks for your help guys!
