2008/11/27 Bob Lee <[EMAIL PROTECTED]>
> We still need to fix the problem w/ the thread local in Injector by using
> an Object[] instead of a Context[].
>
I tried that and it didn't seem to make any difference: I can
unload it from an plain OSGi framework, but not GlassFish
I can even unload without the thread-local change, as long
as I 'kick-the-tires' of GC enough times (this is for a simple
test so perhaps the thread local doesn't come into play)
but it seems that GlassFish is still using another layer for
WAR packaged web-apps, and this layer is having trouble
unloading Guice where the vanilla OSGi loader does not
very odd, oh well - will investigate further when I have time
> On Nov 26, 2008 9:31 PM, "Stuart McCulloch" <[EMAIL PROTECTED]> wrote:
>
> 2008/11/27 Gili Tzabari <[EMAIL PROTECTED]>
>
>>
>> > Stuart McCulloch wrote: > > so it's not a matter of what's keeping the
>> Finalizer alive - you need ...
>>
>> > By "Guice classloader" you mean the CL used to invoke
>> Guice.createInjector?
>>
>
> it depends how you're deploying it - if you're using a WAR then that should
> be the one
>
> > Is System.setProperty("guice.custom.loader", "true") supposed to
> make a > difference?
>
> the patched guice jar I'm using has this enabled by default, but this is
> more about eager unloading of proxy classes
>
>
> > > > you should instead look for any references from outside of the Guice
> > > classloader, > > tha...
>
> ok - otherwise I'll try to put together a simple example later today when I
> have time
>
>
>> Thanks,
>> Gili
>>
>
> --
> Cheers, Stuart
>
> >
>
--
Cheers, Stuart
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/google-guice?hl=en
-~----------~----~----~----~------~----~------~--~---
