Everything seems to be working fine using the trunk code, and seems to have been for a while. I'm not creating any contexts explicitly, though.
The only time I was able to see a problem was with 1.1m5. I'm going to revert the FinderFactoryModule code to use Context.getCurrent() by default. Anyone with special circumstances can subclass FinderFactoryModule to use Application.getContext().getCurrent() if they need to. --tim On Tue, Aug 19, 2008 at 6:51 AM, Jerome Louvel <[EMAIL PROTECTED]>wrote: > Hi Tim and Chris, > > I've done some changes this morning that preserve the parent current > context if the child Restlet has a null context. It may solve your issue as > well but I don't have time to try Tim's code myself. > > If you can try the fresh snapshot that includes the changes: > http://www.restlet.org/downloads/snapshot.zip > > Best regards, > Jérôme Louvel > -- > Restlet ~ Founder and Lead developer ~ > http://www.restlet.org > Noelios Technologies ~ Co-founder ~ http://www.noelios.com > > ------------------------------ > *De :* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *De la part de* Tim > Peierls > *Envoyé :* lundi 18 août 2008 20:50 > *À :* discuss@restlet.tigris.org > *Objet :* Re: Guice and 1.1m5 > > Sounds as though the call to Context.getCurrent() is somehow happening in > a thread for which Context.setCurrent has not been called. I can reproduce > the behavior with 1.1m5, so when I get a chance I'll dig deeper. I'm > assuming this is not very urgent, given the > Application.getCurrent().getContext() workaround. > > --tim > > On Mon, Aug 18, 2008 at 12:38 PM, Chris Lee <[EMAIL PROTECTED]>wrote: > >> Jerome Louvel <jerome.louvel <at> noelios.com> writes: >> >> > 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. >> >> Jerome, I checked out revision 3688 from SVN, and had the same problems. I >> used >> Tim's code unmodified and passing a child context to the application >> rather than >> the component's context, and both times Context.getCurrent() is null in >> the >> finder. >> >> Thanks! >> >> >
