DPML Notify

[mcconnell at BerliOS <mcconnell AT mail.berlios.de>]

Author: mcconnell
Date: 2007-03-15 05:25:07 +0100 (Thu, 15 Mar 2007)
New Revision: 1913

Modified:
   trunk/central/site/src/docs/metro/component/semantics/context.xml
   trunk/central/site/src/docs/metro/component/semantics/parts.xml
Log:
more docs

Modified: trunk/central/site/src/docs/metro/component/semantics/context.xml
===================================================================
--- trunk/central/site/src/docs/metro/component/semantics/context.xml   
2007-03-14 07:48:05 UTC (rev 1912)
+++ trunk/central/site/src/docs/metro/component/semantics/context.xml   
2007-03-15 04:25:07 UTC (rev 1913)
@@ -62,7 +62,7 @@
         <ol>
           <li>Explicit assertion using the <a 
href="../annotation/context.html">
           context annotation</a> marker.</li>
-          <li>Implicitly resolved by locating an inner interface with the 
+          <li>Implicitly resolved by locating an inner interface within the 
           target component class named <tt>Context</tt>.</li>
         </ol>
         
@@ -108,13 +108,16 @@
         
       </subsection>
       
-      <subsection name="Separation of requirements from solutions">
+      <subsection name="Technical Note">
       
         <p>
-        Context interface declare the dependencies that a component
-        has on its environment.  The solution to these dependecy constraints 
-        are handled via <a href="../profile/index.html">packaged profiles</a>
-        and/or independent <a href="../directive/index.html">deployment 
directives</a>.
+        A Context interface declares the dependencies that a component
+        has on its environment.  The solution to these dependency 
constraints 
+        is a function of the container implementation.  The Metro runtime
+        provides services supporting preconfigured 
+        <a href="../profile/index.html">packaged profiles</a> combined with
+        url based <a href="../directive/index.html">deployment directives</a>
+        as the default DPML deployment solution.
         </p>
         
       </subsection>

Modified: trunk/central/site/src/docs/metro/component/semantics/parts.xml
===================================================================
--- trunk/central/site/src/docs/metro/component/semantics/parts.xml     
2007-03-14 07:48:05 UTC (rev 1912)
+++ trunk/central/site/src/docs/metro/component/semantics/parts.xml     
2007-03-15 04:25:07 UTC (rev 1913)
@@ -12,8 +12,29 @@
     <section name="Component Parts">
     
       <p>
+      The DPML runtime differentials between services and resources supplied
+      to a component as opposed to the internal collection of components that
+      collectively define the enclosing component. In effect context 
information
+      deals with existing resources supplied to a component to fulfill its 
+      runtime dependencies, wheras the parts of a component deal with the 
+      structal composition of a componet.  In technical terms - the parts of 
a 
+      component can be viewed as strongly aggregated subsidiary component 
(i.e
+      the destruction of the enclosing component implies the destruction of 
the 
+      enclosed components).
       </p>
       
+      <p>
+      The Metro runtime provides support for the (a) a component's 
declaration of 
+      the internal components it is managing, (b) the framework for internal
+      component assignment, and (c) component access in a container 
independent 
+      fashion. Declaration of internal stucture presumptions is achieved 
though 
+      a <tt>Parts</tt> interface contract.  Internal part composition 
criteria is
+      declared via a constructor parameter that is recognized as a parts 
interface.
+      Metro provides annotations enabling the delcatration of an interface 
as compliant
+      with the parts contract model, togeyther with pattern-based 
recognition of 
+      an inner-interface named <tt>Parts</tt> relative to the target 
component class.
+      </p>
+      
     </section>
 
   </body>