notify-dpml AT lists.ibiblio.org
Subject: DPML Notify
List archive
r1509 - in trunk/main/central/src/docs/metro/directives: component type/info
- From: mcconnell at BerliOS <mcconnell AT mail.berlios.de>
- To: notify-dpml AT lists.ibiblio.org
- Subject: r1509 - in trunk/main/central/src/docs/metro/directives: component type/info
- Date: Thu, 8 Jun 2006 06:25:39 +0200
Author: mcconnell
Date: 2006-06-08 06:25:35 +0200 (Thu, 08 Jun 2006)
New Revision: 1509
Modified:
trunk/main/central/src/docs/metro/directives/component/index.xml
trunk/main/central/src/docs/metro/directives/type/info/index.xml
Log:
add missing info about lifestyle policy
Modified: trunk/main/central/src/docs/metro/directives/component/index.xml
===================================================================
--- trunk/main/central/src/docs/metro/directives/component/index.xml
2006-06-08 02:00:46 UTC (rev 1508)
+++ trunk/main/central/src/docs/metro/directives/component/index.xml
2006-06-08 04:25:35 UTC (rev 1509)
@@ -37,7 +37,34 @@
to the container).</td>
</tr>
<tr>
+ <td><tt>lifestyle</tt></td>
+ <td>The component lifestyle. Allowable values include
+ <tt>singleton</tt>, <tt>thread</tt>, and <tt>transient</tt>.
+ A component declaring the <tt>singleton</tt> lifestyle may be
+ shared across all consumers within the JVM (i.e. the potential
+ for concurrent access will exist). A component declaring
+ the <tt>thread</tt> lifestyle policy may have a set of
instances
+ corresponding to the number of threads requesting access. A
+ component declaring the <tt>transient</tt> lifestyle will
+ instantiated for each access request. The default lifestyle
+ policy is <tt>thread</tt> unless the component is associated
+ with an underlying type defintion in which case the type
lifestyle
+ value will apply.</td>
+ </tr>
+ <tr>
<td><tt>collection</tt></td>
+ <td>The component garbage collection policy. Allowable
+ values include <tt>weak</tt>, <tt>soft</tt> and <tt>hard</tt>.
+ A component type declaring a <tt>weak</tt> collection policy
will
+ be garbage collected at the discretion of the JVM. A component
+ declaring a <tt>soft</tt> collection policy will be garbage
+ collected in the event of memory contention. A component
+ declaring the <tt>hard</tt> collection policy will remain in
+ memory for the lifetime of the JVM unless explicitly removed
+ via a management system or controlling application.</td>
+ </tr>
+ <tr>
+ <td><tt>collection</tt></td>
<td>Overrides the component garbage collection policy
(optional). Allowable
values include <tt>WEAK</tt>, <tt>SOFT</tt> and <tt>HARD</tt>.
A component declaring a <tt>WEAK</tt> collection policy will
Modified: trunk/main/central/src/docs/metro/directives/type/info/index.xml
===================================================================
--- trunk/main/central/src/docs/metro/directives/type/info/index.xml
2006-06-08 02:00:46 UTC (rev 1508)
+++ trunk/main/central/src/docs/metro/directives/type/info/index.xml
2006-06-08 04:25:35 UTC (rev 1509)
@@ -58,7 +58,7 @@
</tr>
<tr>
<td><tt>threadsafe</tt></td>
- <td>Declares the component implementation as threadsafe.
Allo0wable
+ <td>Declares the component implementation as threadsafe.
Allowable
values are <tt>true</tt> or <tt>false</tt>.</td>
</tr>
</table>
- r1509 - in trunk/main/central/src/docs/metro/directives: component type/info, mcconnell at BerliOS, 06/08/2006
Archive powered by MHonArc 2.6.24.