notify-dpml AT lists.ibiblio.org
Subject: DPML Notify
List archive
r1924 - trunk/central/site/src/docs/metro/component/lifecycle
- From: mcconnell at BerliOS <mcconnell AT mail.berlios.de>
- To: notify-dpml AT lists.ibiblio.org
- Subject: r1924 - trunk/central/site/src/docs/metro/component/lifecycle
- Date: Mon, 19 Mar 2007 09:06:14 +0100
Author: mcconnell
Date: 2007-03-19 09:06:13 +0100 (Mon, 19 Mar 2007)
New Revision: 1924
Modified:
trunk/central/site/src/docs/metro/component/lifecycle/index.xml
trunk/central/site/src/docs/metro/component/lifecycle/state.xml
Log:
more docs
Modified: trunk/central/site/src/docs/metro/component/lifecycle/index.xml
===================================================================
--- trunk/central/site/src/docs/metro/component/lifecycle/index.xml
2007-03-19 07:30:36 UTC (rev 1923)
+++ trunk/central/site/src/docs/metro/component/lifecycle/index.xml
2007-03-19 08:06:13 UTC (rev 1924)
@@ -23,6 +23,12 @@
</ul>
<p>
+ The declaration of a state transition model is handled though an XML
document
+ collocated with the component class using the
<tt>[classname].xgraph</tt> filename
+ convention.
+ </p>
+
+ <p>
The initialization and termination phases can be expressed in terms of
a
state-transition graph. On initialization a component is establish in
an
initial state. That state may declare initialization transitions to
be applied
@@ -34,12 +40,6 @@
</p>
<p>
- The declaration of a state transition model is handled though an XML
document
- collocated with the component class using the
<tt>[classname].xgraph</tt> filename
- convention.
- </p>
-
- <p>
The lifecycle graph declares a state heirachy and transition available
in any
given state. During runtime, a component may (as a result of
initialization) be
established in a particular runtime state. That state is referred to
as the
Modified: trunk/central/site/src/docs/metro/component/lifecycle/state.xml
===================================================================
--- trunk/central/site/src/docs/metro/component/lifecycle/state.xml
2007-03-19 07:30:36 UTC (rev 1923)
+++ trunk/central/site/src/docs/metro/component/lifecycle/state.xml
2007-03-19 08:06:13 UTC (rev 1924)
@@ -67,72 +67,6 @@
</section>
- <section name="Example">
-
-<pre><state xmlns="dpml:state"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-
- <trigger event="initialization">
- <transition name="start" target="started">
- <operation name="startup" method="start"/>
- </transition>
- </trigger>
-
- <state name="started">
- <trigger event="termination">
- <apply id="stop"/>
- </trigger>
- <transition name="stop" target="../stopped">
- <operation name="stop" method="stop"/>
- </transition>
- </state>
-
- <state name="stopped">
- <transition name="start" target="../started">
- <operation name="start" method="start"/>
- </transition>
- </state>
-
-</state></pre>
-
-
- </section>
-
- <section name="Technical Note">
-
- <subsection name="Importing a State Graph">
-
- <p>
- As an alternative to the above attributes and nested elements, a
- state graph may be imported from an external source. For example, a
- graph defining a common lifecycle model can be shared across
multiple
- components.
- </p>
-
- </subsection>
-
- <subsection name="XGraph Resource">
-
- <p>
- The following example demonstrates the import of a state graph
- using the <tt>class</tt> attribute. The classname supplied must
- be a class that has a collocated <tt>.xgraph</tt> resource. The
- <tt>.xgraph</tt> resource is an XML file containing a state model
- described using the same attribute and element combinanations as
- described above.
- </p>
-
-<pre><![CDATA[
-<c:type name="http" class="net.dpml.http.impl.HttpServerImpl"
threadsafe="true">
- <state class="net.dpml.activity.Startable"/>
-</c:type>
-]]></pre>
-
- </subsection>
-
-
- </section>
-
</body>
</document>
- r1924 - trunk/central/site/src/docs/metro/component/lifecycle, mcconnell at BerliOS, 03/19/2007
Archive powered by MHonArc 2.6.24.