Ok, Raymond, this is useful. So what it does seem to come down to is binding selection. It's not clear from your comment whether you believe this is already done somewhere or whether this is a new piece of functinality that we need to add.
From what I see in the code I think we do need a way of marking which
binding is intended to be active between any particular reference/service pair. When you say "Should it be done when we flatten the model?" do you mean when the components that each reference targets are resolved or do you mean later on?. The issue I see at resoltuion time is that a reference holds bindings and targets independently. So we could change the model to allow us to create a relationship between target and binding at this point. Alternatively we can make the change at wire generation time where we have the wire structures to hold this relationship. Can you think of scenarios where we don't want to be deterministic and include this information in the model? Regards Simon
