Daniel:
Based on your feedback and some more thinking from myself I've just committed some code under the composition package that enables two modes of dependency qualification. Consider the following example:
<container name="root">
<component name="comp" class="org.apache.playground.SomeComponent"/>
<container name="xxx">
<component name="comp-2" class="org.apache.playground.AnotherComponent">
<dependencies>
<dependency key="first-key" source="../comp"/>
<dependency key="second-key">
<select feature="color" value="red" match="equals"/>
<select feature="publisher" value="ASF" match="exists" optional="true"/>
</dependency>
</dependencies>
</component>
</container>
</container>
This covers two approaches (a) delection by named source component, and (b) selection by filtering againt a criteria. The first option is based on your suggestion with a small change to the attribute name (I chose to use "source" instead of "provider" simply because at this point in the process the provider is resolved relative to a source address - the term provider is more applicable to the comoosition/model package where we are dealiong with actual solutions). If a source address is not declared, selection constraints kick-in. If there are not selection constraints, then life containes as per normal auto-assembly semantics.
This should cover both of our requirements.
Let me know if you see any problems (or suggestions for improvement, etc.).
Cheers, Steve.
p.s. The composition package is not part of the Merlin runtime just yet.
SJM
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
