On Aug 20, 2008, at 5:46 PM, BJ Hargrave wrote:
[EMAIL PROTECTED] wrote on 2008/08/17 08:29:15 PM:
> Re: [osgi-dev] Question on Bundle#update()
>
> Ikuo Yamasaki
>
> to:
>
> OSGi Developer Mail List
>
> 2008/08/17 08:38 PM
>
> Sent by:
>
> [EMAIL PROTECTED]
>
> Please respond to OSGi Developer Mail List <[email protected]>
>
> Thank you for answering my question, BJ.
>
> I got it.
>
> But, what does "this bundle tries to change its own state" mean in
the
> statement of the spec ?
It means a bundle calling, for example, stop on its own Bundle
object. Since the stop contract says the Bundle has to stop doing
things, then when Bundle.stop returns, the bundle is still
executing. This is an awkward state :-)
Do implementations really test for this? The implementation to catch
this seems straightforward using class loading/CGLIB mumbo jumbo but
still adds overhead in terms of both space, execution, and the code to
implement it in the framework. I can imagine some kind of chain of
calls where a bundle does not directly stop itself.
Seems like an odd rule to put into the spec.
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
