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! > >
