BJ Hargrave wrote:
> BJ> > Could you tell me which descriptions in the spec address the
use of
> BJ> > static policy with
> BJ> > multiple cardinality in order to answer Q1 and Q2 ?
> BJ>
> BJ> See 112.5.7: "When a component configuration's reference is
satisfied,
> BJ> there is a set of
> BJ> zero or more target services for that reference. When the component
> BJ> config-
> BJ> uration is activated, a subset of the target services for each
reference
> BJ> are
> BJ> bound to the component configuration. The subset is chosen by the
cardi-
> BJ> nality of the reference. See Reference Cardinality on page306."
>
> Although I understand the underlieing idea,
> I don't think I am convinced completely regarding the description
ofthe spec.
>
> I don't see any discription in the spec about the case that
> a new target service to be bound gets found while a componet
> configuration still keeps satisfied.
>
> Please think about Q2 I had posted.
>
> According to the description in "112.5.2 Satisfied",
> the all three conditions described in 112.5.2 still keep true and
> the component configuration will NOT become unsatisfied.
>
> Therefore it should not be deactivated for answer of Q2.
>
> I mean, the spec should be clarified for this point, shouldn't it?
You are right. I misspoke in my prior mail for Q2. In Q2 then, since the
component is satisfied, when a new service A is registered, the
component should remain activated.
I disagree. Static policy requires deactivation of the component for any
change of any of its references. The bind method of a component with a
static policy must be called before the component is activated (see
112.4.7 Reference Element). I think we should add a clarification in the
chapter where the static policy is described to avoid further confusions.
Stoyan
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
