> Thanks Carsten, that was my expectation but I was waiting for the “inspect > cap service” output to confirm. > > One thing that can be quite confusing is that the service references, with > cardinality of 1..1, are described as both satisfied and unbound. This sounds > like a contradiction until you realise the component has not yet been > instantiated. I assume that SCR at this point does know which services it > *will* bind when the component is activated… maybe these could be shown here? > Hmm, yeah we could do that - on the other hand "unbound" means it's satisfied, otherwise it would state the reference as "unsatisfied" :) Maybe, it's more a wording problem?
Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
