> >>> ...The reason I need to hold on to the bundle is to load classes
> >>> using that its classloader at a later point in time...
> >>
> >> Can't you do that using getClass().getClassLoader() on a class that's
> >> inside that bundle?
> >>
> >> I *think* keeping references to Bundle objects is fi
On Apr 18, 2013, at 16:00 , Robert Munteanu wrote:
>>> ...The reason I need to hold on to the bundle is to load classes using
>>> that its classloader at a later point in time...
>>
>> Can't you do that using getClass().getClassLoader() on a class that's inside
>> that bundle?
>>
>> I *think* k
> > ...The reason I need to hold on to the bundle is to load classes using
> > that its classloader at a later point in time...
>
> Can't you do that using getClass().getClassLoader() on a class that's inside
> that bundle?
>
> I *think* keeping references to Bundle objects is fine if you track t
On Thu, Apr 18, 2013 at 3:24 PM, Robert Munteanu wrote:
> ...The reason I need to hold on to the bundle is to load classes using that
> its classloader
> at a later point in time...
Can't you do that using getClass().getClassLoader() on a class that's
inside that bundle?
I *think* keeping refer
4 matches
Mail list logo