On 12/08/16 12:02, Carsten Ziegeler wrote:
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?
I think that would be misleading because when the bundle composition changes before activation is needed then a different resolution can/will be activated.
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
-- Ferry Huberts --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
