DPML Notify

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

Author: mcconnell
Date: 2007-04-23 18:24:44 +0200 (Mon, 23 Apr 2007)
New Revision: 1983

Modified:
   trunk/central/site/src/docs/metro/component/policies/index.xml
   trunk/central/site/src/docs/metro/parts/strategy/index.xml
Log:
minor improvements to documentation

Modified: trunk/central/site/src/docs/metro/component/policies/index.xml
===================================================================
--- trunk/central/site/src/docs/metro/component/policies/index.xml      
2007-04-23 16:24:11 UTC (rev 1982)
+++ trunk/central/site/src/docs/metro/component/policies/index.xml      
2007-04-23 16:24:44 UTC (rev 1983)
@@ -18,11 +18,48 @@
       decisions as to when a new instance of a component is required), and 
garbage 
       <a href="collection.html">collection</a> policies (controlling the 
strength 
       of internal references between a component model and its instances).
+      </p>
+      
+      <p>
       Runtime policies may be declared via class 
       <a href="../annotation/index.html">annotations</a> or through related 
       attributes in packaged <a href="../profile/index.html">profiles</a> 
       or <a href="../directive/index.html">component directives</a>. 
       </p>
+      
+      <p>
+      Runtime policies are summarasied under the following table.
+      </p>
+      
+      <table>
+        <tr>
+          <td><a href="activation.html">Activation</a></td>
+          <td>
+            Enables declaration of activation on STARTUP or activation
+            on DEMAND policy.
+          </td>
+        </tr>
+        <tr>
+          <td><a href="lifestyle.html">Lifestyle</a></td>
+          <td>
+            Used to declare the strategy to be applied by a container when
+            a request for access to a component is received. The policy 
+            provides for the selection of either a SINGLETON scope within
+            which requests are shared across multiple consumers and thread
+            boundaries, THREAD in which a component instance is created for 
+            based on thread identity, and TRANSIENT under which a new 
component
+            instance is created per request.
+          </td>
+        </tr>
+        <tr>
+          <td><a href="collection.html">Collection</a></td>
+          <td>
+            Declaration of a garbage collection policy controlling the 
+            strength of internal references between a component model and 
its 
+            instances.
+          </td>
+        </tr>
+      </table>
 
     </section>
 

Modified: trunk/central/site/src/docs/metro/parts/strategy/index.xml
===================================================================
--- trunk/central/site/src/docs/metro/parts/strategy/index.xml  2007-04-23 
16:24:11 UTC (rev 1982)
+++ trunk/central/site/src/docs/metro/parts/strategy/index.xml  2007-04-23 
16:24:44 UTC (rev 1983)
@@ -40,13 +40,13 @@
     <complexType name="StrategyType" abstract="true"/>]]></pre>
         
         <p>
-        The Metro runtime model defines a concrete <a 
href="../../component/directive/component.html">
+        The Metro runtime model defines a concrete <a 
href="../../component/directive/index.html">
         component strategy</a> under the <tt>dpml:metro</tt> namespace that 
is used to 
         define the resources, services, and internal composition of an 
object. A second 
-        concrete strategy defintion named <tt>resource</tt> (uder the 
<tt>dpml:depot</tt>
+        concrete strategy defintion named <tt>resource</tt> (uder the 
<tt>dpml:antlib</tt>
         namespace) is used by the Depot build system to define antlib 
loading criteria.
         If a foreign strategy element is declared the associated schema is 
resolved 
-        buy locating a class implementing the 
<tt>org.w3c.dom.ls.LSResourceResolver</tt>
+        by locating a class implementing the 
<tt>org.w3c.dom.ls.LSResourceResolver</tt>
         service (via java.util.ServiceLoader).  The runtime strategy handler 
will be 
         resolved by reading a uri value from an attribute named 
<tt>handler</tt>.  The
         uri is used to identify a plug-in part supporting the runtime 
handling of the