On Wed, May 19, 2010 at 2:13 AM, Richard S. Hall <[email protected]>wrote:
> On 5/18/10 20:06, Justin Edelson wrote: > >> I know there was some confusion about the handling of SCR static >> optional references in the past, so could someone confirmt that a static >> optional reference will do this: >> >> Assume Component 1 has a static optional reference to Component 2 >> >> 1) Component 1 activated with null reference to Component 2. >> 2) Component 2 activated. >> 3) Component 1 automatically deactivated and reactivated not with >> non-null reference to Component 2 >> >> > > No, this should not be the case. Static is a snapshot at activation time. > After the snapshot, the component will only be impacted if any services it > is using go away. In your case, since it is an arrival, the component isn't > impacted. > > Thanks Richard. This makes a lot of sense. Justin > 4) Component 3 deactivated >> >> > > I assume you mean Component 2. > > > 5) Component 1 automatically deactivated and reactivated not with null >> reference to Component 2 >> >> > > This would be true if Component 1 were activated with a reference to > Component 2 in the first place, but for your scenario, it would have never > gotten a reference to Component 2 in the first place in step (3). > > -> richard > > Thanks, >> Justin >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
