] *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
D] [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
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()
Jerome Louvel 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 unmo
:06
A : discuss@restlet.tigris.org
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.re
Chris Lee leeprinting.com> writes:
>
> Jonathan Hall gmail.com> writes:
>
> > Maybe down to: "Important Context Changes" dated 29/07/2008
> >
> > "- the Context instance given to an application (or any Restlet
> > actually) will be the one effectively used. If parameters are set, they
> > w
tp://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 : discuss@restlet.tigris.org
Objet : Re: Guice and 1.1m5
Tim Peierls peierls.net> writes:
>
> In which case the fix for Chris might b
Tim Peierls 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
gmail.com> wrote:
You wou
Jonathan Hall gmail.com> writes:
> Maybe down to: "Important Context Changes" dated 29/07/2008
>
> "- the Context instance given to an application (or any Restlet
> actually) will be the one effectively used. If parameters are set, they
> will be directly and permanently accessible. If none is
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.
--tim
On Thu, Aug 14, 2008 at 4:05 AM, Jonathan Hall <[EMAIL PROTECTED]> wrote:
> Maybe down to: "Important Conte
Maybe down to: "Important Context Changes" dated 29/07/2008
"- the Context instance given to an application (or any Restlet
actually) will be the one effectively used. If parameters are set, they
will be directly and permanently accessible. If none is given, a null
context will be returned by
Chris,
I managed to get some slightly less limited connectivity out here in the
Maine woods.
When you do discover what changes between m4 and m5 caused
Context.getContext() to return null in m5, I think it might be a good idea
to change FinderFactoryModule so that subclasses can override the defa
Hey guys, I followed Tim Peierls' excellent tutorial on using Guice in Restlets
(found at
http://tembrel.blogspot.com/2008/07/resource-dependency-injection-in.html) and
found that, while it works quite well with 1.1m4, it does not work with 1.1m5.
The error seems to be in the Guice Provider for th
13 matches
Mail list logo
