notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

r1951 - trunk/central/site/src/docs/station/plan

From: mcconnell at BerliOS <mcconnell AT mail.berlios.de>
To: notify-dpml AT lists.ibiblio.org
Subject: r1951 - trunk/central/site/src/docs/station/plan
Date: Fri, 6 Apr 2007 19:24:24 +0200

Author: mcconnell
Date: 2007-04-06 19:24:23 +0200 (Fri, 06 Apr 2007)
New Revision: 1951

Added:
trunk/central/site/src/docs/station/plan/include.xml
Removed:
trunk/central/site/src/docs/station/plan/entry.xml
Log:

Deleted: trunk/central/site/src/docs/station/plan/entry.xml
===================================================================
--- trunk/central/site/src/docs/station/plan/entry.xml 2007-04-06 17:21:07
UTC (rev 1950)
+++ trunk/central/site/src/docs/station/plan/entry.xml 2007-04-06 17:24:23
UTC (rev 1951)
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-
-<document>
-
- <properties>
- <author email="mcconnell AT dpml.net">Stephen McConnell</author>
- <title>DPML Station Deployment Plan Entry Directive</title>
- </properties>
-
- <body>
-
- <section name="Entry Directive">
-
- <subsection name="Description">
-
- <p>
- Definition of a deployment entry.
- </p>
-
- </subsection>
-
- <subsection name="Attributes">
- <table>
- <tr>
- <td><tt>key</tt></td>
- <td>A unique key identitying the deployment entry.</td>
- </tr>
- <tr>
- <td><tt>uri</tt></td>
- <td>A uri identifying a <tt>part</tt> or <tt>appliance</tt>
datatype.</td>
- </tr>
- </table>
-
- </subsection>
-
- </section>
-
- <section name="Technical Tote">
-
- <p>
- The current implementation recognizes the
- <a href="../../metro/parts/index.html"><tt>part</tt></a> datatype and
the station
- <a href="../appliance/index.html"><tt>appliance</tt></a> datatype.
- Part datatypes are resolved to a component definition deployed
- within the same JVM as the station. Appliance datatypes are used to
construct a
- separate JVM process (controlled by the station) hosting a component
established
- relative to the appliace codebase argument.
- </p>
-
- </section>
-
- </body>
-
-</document>
-

Copied: trunk/central/site/src/docs/station/plan/include.xml (from rev 1931,
trunk/central/site/src/docs/station/plan/entry.xml)
===================================================================
--- trunk/central/site/src/docs/station/plan/entry.xml 2007-03-24 06:05:14
UTC (rev 1931)
+++ trunk/central/site/src/docs/station/plan/include.xml 2007-04-06
17:24:23 UTC (rev 1951)
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<document>
+
+ <properties>
+ <author email="mcconnell AT dpml.net">Stephen McConnell</author>
+ <title>DPML Station Deployment Plan Include Directive</title>
+ </properties>
+
+ <body>
+
+ <section name="Entry Directive">
+
+ <subsection name="Description">
+
+ <p>
+ Definition of a deployment include entry by reference.
+ </p>
+
+ </subsection>
+
+ <subsection name="Attributes">
+ <table>
+ <tr>
+ <td><tt>key</tt></td>
+ <td>A unique key identitying the deployment entry.</td>
+ </tr>
+ <tr>
+ <td><tt>uri</tt></td>
+ <td>A uri identifying a <tt>part</tt> or <tt>appliance</tt>
datatype.</td>
+ </tr>
+ </table>
+
+ </subsection>
+
+ </section>
+
+ <section name="Technical Note">
+
+ <p>
+ The current implementation recognizes the
+ <a href="../../metro/parts/index.html"><tt>part</tt></a> datatype and
the station
+ <a href="appliance/index.html"><tt>appliance</tt></a> datatype.
+ Part datatypes are resolved to a component definition deployed
+ within the same JVM as the station. Appliance datatypes are used to
construct a
+ separate JVM process (controlled by the station) hosting a component
established
+ relative to the appliace codebase argument.
+ </p>
+
+ </section>
+
+ </body>
+
+</document>
+

r1951 - trunk/central/site/src/docs/station/plan, mcconnell at BerliOS, 04/06/2007