NEW ISSUE: Clarifying the Domain Composite Infoset

[ashok malhotra <ashok.malhotra@oracle.com>]

Raymond Feng and I have been exchanging mail on the list.  This issue 
arose as a result of that interaction.

Raymond makes  two points about the  Domain Composite Infoset:

1. The assembly spec defines a URI  scheme for embedded composites.   
But the URI needs to be
surfaced in an attribute so that it can be selected using an XPath 
expression.

2. Raymond argues that the embedded composites need to be inlined rather 
that referenced. 
If the Infoset corresponds to:

[1]
<composite xmlns:ns2="http://ns2 <http://ns2/>" ...>
  <component name="Component1" *uri="Component1"*>
        <implementation.composite name="ns2:InnerComposite"/>
  </component>
</composite>

Applying //component[@uri='Component1/Component2'] against the XML 
doesn't select Component2 as it is NOT an element in the tree. If we 
inline the inner composite into the domain composite as illustrated 
below, the it would work.

[2]
<composite xmlns:ns2="http://ns2 <http://ns2/>" ...>
   <component name="Component1" *uri="Component1**"*>
   <implementation.composite name="ns2:InnerComposite">
       <!-- For demo purpose, Inline the inner composite -->
       <composite targetNamespace="http://ns2 <http://ns2/>" 
name="InnerComposite">
           <service name="Service1" promote="Component2/Service1"/>
           <reference name="ref1" promote="Component2/ref1"/>
           <component name="Component2" *uri="Component1/Component2"*>
                <implementation.java class="sample.Component2Impl"/>
           </component>
        </composite>
   </implementation.composite>
  </component>
</composite>

-- 
All the best, Ashok