Berin,
I could use a little more explanation. The example for Fortress doesn't
help at all in this regard, I apologize for asking for so much detail!
Let's say I am going to implement this format in system.xconf:
<a-things><a-thing1/><a-thing2/></a-things>
<b-things><b-thing1/><b-thing2/></b-things>
I want to use the same selector class for selecting the 2nd-tier components,
so do I specify that in the roles.xconf file as this (which doesn't work,
when I tried):
<roles>
<role name="...AThingsSelector">
<component shorthand="a-things" class="...MySelector" handler="...">
<component shorthand="a-thing1" class="..." handler="..."/>
<component shorthand="a-thing2" class="..." handler="..."/>
</role>
<role name="...BThingsSelector">
<component shorthand="b-things" class="...MySelector" handler="...">
<component shorthand="b-thing1" class="..." handler="..."/>
<component shorthand="b-thing2" class="..." handler="..."/>
</role>
</roles>
So the questions are:
- The role name should have the "Selector" appened so that it matches
the lookup?
- A component with the Selector class should be specified for each role
(MySelector)?
- Can the same Selector class name be used for each role that has
selectable-components?
- Can that selector class be FortressServiceSelector?
- I see that there is special handling for "select" and "default" hints
in AbstractContainer.addComponent(), but where is that specified?
If I can then lookup the Selector, I think I am home free from there, I
could either override DefaultContainer's configure, or have the
ServiceSelector's configure load up the second-tier, nested components in
its configure method? Correct?
Shash
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
