Ikuo Yamasaki wrote:
Hi BJ and all,
Thank you for your comments.
On Thu, 23 Jul 2009 14:19:34 -0400
BJ Hargrave <[email protected]> wrote:
BJ> > Please think about Q2 I had posted.
BJ> >
BJ> > According to the description in "112.5.2 Satisfied",
BJ> > the all three conditions described in 112.5.2 still keep true and
BJ> > the component configuration will NOT become unsatisfied.
BJ> >
BJ> > Therefore it should not be deactivated for answer of Q2.
BJ> >
BJ> > I mean, the spec should be clarified for this point, shouldn't it?
BJ>
BJ> You are right. I misspoke in my prior mail for Q2. In Q2 then, since the
BJ> component is satisfied, when a new service A is registered, the component
BJ> should remain activated.
So, how the current Equinox DS impl works is a bug ? or The spec should
be rewrite to be clarified ?
I don't consider the current behavior of Equinox DS as a bug. The bind
method of a component with a static policy must be called before the
component is activated (see 112.4.7 Reference Element).
c.f. In Equinox DS impl, activation will be done after deactivation is
done.
Is there anybody who can tell how do other DS impls work ?
I mean felix, knopflerfish or others...
=======
Ikuo YAMASAKI
Stoyan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
