DPML Notify

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

Author: mcconnell
Date: 2006-03-28 07:08:20 +0200 (Tue, 28 Mar 2006)
New Revision: 1279

Modified:
   trunk/main/central/etc/docs/images/metro/apis.png
   trunk/main/central/src/art/apis.ppt
   trunk/main/central/src/docs/metro/runtime/index.xml
Log:
clean-up metro runtime description

Modified: trunk/main/central/etc/docs/images/metro/apis.png
===================================================================
(Binary files differ)

Modified: trunk/main/central/src/art/apis.ppt
===================================================================
(Binary files differ)

Modified: trunk/main/central/src/docs/metro/runtime/index.xml
===================================================================
--- trunk/main/central/src/docs/metro/runtime/index.xml 2006-03-28 02:33:27 
UTC (rev 1278)
+++ trunk/main/central/src/docs/metro/runtime/index.xml 2006-03-28 05:08:20 
UTC (rev 1279)
@@ -13,7 +13,7 @@
 
       <p>
       The Metro Runtime is an application that implements a multi-layered 
system model.
-      The following illustration depicts the principal sub-system (higher 
level blocks 
+      The following illustration depicts the principal sub-system APIs 
(higher level blocks 
       are dependent on immediate low-lever blocks).
       </p>
 
@@ -22,11 +22,11 @@
       <subsection name="Metro API">
 
         <p>
-        A <tt>part</tt> is a network accessible datatype
-        that associates a controller with a component deployment profile. 
The 
+        A <tt>component</tt> part is a network accessible datatype
+        that associates a controller with a deployment profile. The 
         deloyment profile references a component type.  The component type 
may
         be implementated using a collection of local or remote component 
parts.
-        The Metro API defines concrete datatypes for component type 
defintions, 
+        The Metro API defines concrete datatypes for component type 
definitions, 
         deployment scenarios, and an extended management model.
         </p>
 
@@ -39,37 +39,38 @@
             assumptions asserted by the implementation, logging assumptions
             and defaults, etc.  A type may also contain an implemention 
description
             in the form of a collection of internal parts.  This information 
is cached 
-            under the <tt>.type</tt> resource (an XML document encoded to 
JSR-57) for 
-            use by deployment tools and the runtime system.
+            under the <tt>.type</tt> resource (in XML) for use by deployment 
tools 
+            and the runtime system.
           </li>
           <li>
             <a href="parts/index.html">directive:</a> 
-            a XML component definition referencable via the <tt>artifact</tt>
+            an XML component definition referencable via the 
<tt>artifact</tt>
             uri using the <tt>part</tt> type identifier.  The part directive 
contains 
             the default deployment profile including the definition of 
             the component inital context, dependency solutions, and any 
related 
             configuration information.  The directives serves as the initial 
data 
-            used to establish a component model.
+            used to establish a component model.  The component definition 
may contain
+            nested component definitions as parts of its internal structure.
           </li>
         </ul>
 
       </subsection>
 
-      <subsection name="Part API">
+      <subsection name="Component API">
 
         <p>
-        The Part API is the core API dealing with component composition and 
is 
+        The Component API deals with component composition and is 
         central to the platforms ability to support concurrent deployment of 
different 
         container implementations.  The Metro system is the reference 
implementation
-        of the Part API.
+        of the Component API.
         </p>
 
         <p>
         Using a network accessible <tt>part</tt> datastructrues, the Metro 
         runtime provides support for the creation of a <tt>Component</tt> 
via 
-        a <tt>Controller</tt>. The <tt>Component</tt> handles scopped 
requests 
-        for locating service providers and establishment of managed 
-        <tt>Provider</tt>(s).
+        a <tt>Controller</tt>. The <tt>Component</tt> handles requests 
+        for locating service providers and the establishment of the 
underlying 
+        component.
         </p>
 
         <ul>
@@ -88,7 +89,16 @@
 
       </subsection>
 
+      <subsection name="Part API">
 
+        <p>
+        The Part API deals with a generic deployment package.  XML part 
descriptions
+        include a complete classloader chain definition and the declaration 
of a 
+        deployment strategy.  
+        </p>
+
+      </subsection>
+
     </section>
 
   </body>