notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

r1885 - in trunk/central/site/src/docs: metro/concepts util/depot/tutorials util/transit/tutorials

From: mcconnell at BerliOS <mcconnell AT mail.berlios.de>
To: notify-dpml AT lists.ibiblio.org
Subject: r1885 - in trunk/central/site/src/docs: metro/concepts util/depot/tutorials util/transit/tutorials
Date: Wed, 7 Mar 2007 05:37:01 +0100

Author: mcconnell
Date: 2007-03-07 05:36:58 +0100 (Wed, 07 Mar 2007)
New Revision: 1885

Added:
trunk/central/site/src/docs/util/depot/tutorials/101.xml
Modified:
trunk/central/site/src/docs/metro/concepts/index.xml
trunk/central/site/src/docs/metro/concepts/ioc.xml
trunk/central/site/src/docs/metro/concepts/navigation.xml
trunk/central/site/src/docs/util/transit/tutorials/repositories.xml
Log:

Modified: trunk/central/site/src/docs/metro/concepts/index.xml
===================================================================
--- trunk/central/site/src/docs/metro/concepts/index.xml 2007-03-07
03:45:30 UTC (rev 1884)
+++ trunk/central/site/src/docs/metro/concepts/index.xml 2007-03-07
04:36:58 UTC (rev 1885)
@@ -11,29 +11,72 @@

<section name="DPML Metro">

- 
- Metro is an advanced component runtime solution.
- 
+ 
+ Metro is an advanced component runtime solution.
+ 

- 
- Metro is an <a href="ioc.html">IOC</a> Container
- that handles the deployment of component-based applications. Beyond
this Metro
- delivers pure framework independent component-driven <a
href="ioc.html">Adaptive
- Context</a> support backed by an <a href="management.html">Active
State</a>,
- <a href="model.html">Model Driven</a>, <a href="parts.html">Part
Based</a>
- system arctitecture.
- 
+ 
+ Metro is an <a href="ioc.html">IOC</a> Container
+ that handles the deployment of component-based applications. Beyond
this Metro
+ delivers pure framework independent component-driven <a
href="ioc.html">Adaptive
+ Context</a> support backed by an <a href="management.html">Active
State</a>,
+ model-driven, part-based system architecture.
+ 

- 
- 
- A broader overview of the issues and challenges related to
component-based
- development is presented in the paper
- <a
href="http://www.mrtc.mdh.se/publications/0953.pdf";>Component-based
- Development Process and Component Lifecycle</a> by Ivica Crnkovic,
Stig Larsson,
- Michel Chaudron.
- 
- 
+ <subsection name="Model Driven">

+ 
+ Metro is a "Model Driven" system in that a central model is
+ the definiative source for runtime information. Within Metro the
complete
+ deployment scenario including the component type internal
datastructure
+ is represented as a remotely accessible model. Modification of the
model
+ via local or remote invocations may have a direct impact on the
application
+ deployment or runtime state. Metro provides a suite of interfaces
dealing
+ with remote control of of the component state machine, activation
policy,
+ garbage collection policies, context state, and redepoloyment
scenario
+ information (including control over component configuration,
parameterization,
+ and individual context entry settings).
+ 
+
+ </subsection>
+
+ <subsection name="Part Based">
+
+ 
+ As part of an overral risk-reduction strategy concerning product
+ evolution Metro incorporates an internal controller
+ management model that enables concurrent execution of different
+ container versions within a single application. This strategy
+ enables changes that would normally be classed as breaking
+ compatibility to be isolated in dynamicaly loaded plugin control
+ subsystems. The end-result is the potential for a composite
+ comoponent to operate seamlessly with components using radicaly
+ different controllers.
+ 
+
+ 
+ This is achived through the combinaton of:
+ 
+
+ <ol>
+ <li>Layered internal container APIs.</li>
+ <li>Component deployment data tagged with supporting system
version</li>
+ <li>Dynamic loading of plugin controllers</li>
+ <li>Controller delegation rules</li>
+ </ol>
+
+ </subsection>
+
+ <subsection name="Related Links">
+ 
+ A broader overview of the issues and challenges related to
component-based
+ development is presented in the paper
+ <a
href="http://www.mrtc.mdh.se/publications/0953.pdf";>Component-based
+ Development Process and Component Lifecycle</a> by Ivica Crnkovic,
Stig Larsson,
+ Michel Chaudron.
+ 
+ </subsection>
+
</section>

</body>

Modified: trunk/central/site/src/docs/metro/concepts/ioc.xml
===================================================================
--- trunk/central/site/src/docs/metro/concepts/ioc.xml 2007-03-07 03:45:30
UTC (rev 1884)
+++ trunk/central/site/src/docs/metro/concepts/ioc.xml 2007-03-07 04:36:58
UTC (rev 1885)
@@ -25,7 +25,7 @@
The first area of control "inversion" relates to the use of
resource
identifiers (URIs) in preference to resource locators (URLs). A
URI
identifies the resource but does not expose information concerning
- location. Through a collection of <a
href="/transit/technical/index.html">
+ location. Through a collection of <a
href="/util/transit/technical/index.html">
URI scheme handlers</a> the Metro platform provides the environment
within
which a component implementation can operate exclusively with URI
references. This moves potential resource handling limitations
from a

Modified: trunk/central/site/src/docs/metro/concepts/navigation.xml
===================================================================
--- trunk/central/site/src/docs/metro/concepts/navigation.xml 2007-03-07
03:45:30 UTC (rev 1884)
+++ trunk/central/site/src/docs/metro/concepts/navigation.xml 2007-03-07
04:36:58 UTC (rev 1885)
@@ -28,8 +28,8 @@
<item name="IOC" href="ioc.html"/>
<item name="Context Aware" href="context.html"/>
<item name="Active Management" href="management.html"/>
- <item name="Model Driven" href="model.html"/>
- <item name="Part Based" href="parts.html"/>
+ 
+ 
</menu>

</body>

Added: trunk/central/site/src/docs/util/depot/tutorials/101.xml
===================================================================
--- trunk/central/site/src/docs/util/depot/tutorials/101.xml 2007-03-07
03:45:30 UTC (rev 1884)
+++ trunk/central/site/src/docs/util/depot/tutorials/101.xml 2007-03-07
04:36:58 UTC (rev 1885)
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<document>
+ <properties>
+ <author email="mcconnell AT osm.net">Stephen McConnell</author>
+ <title>Development Tooling Tutorial</title>
+ </properties>
+
+ <body>
+
+ <section name="Setting up an Index">
+
+ 
+ The Depot build system centralizes information about projects in
+ an index file. This tutorial demonstrates the declaration of a single
+ project and serves as a starting point for the introduction of
+ properties and filters.
+ 
+
+ <subsection name="index.xml">
+
+ 
+ The following index file declares a single project named 'demo'.
+ The basedir of the project is the directory containing the project
+ build content and is the path that the Depot tool uses to locate
+ the project's build.xml file. Basedir values are resolved relative
to
+ the basedir of the enclosing entity - in this case the
<tt><index></tt>
+ is the enclosing entity so the basedir is resolved relative to the
+ directory containing the index file.
+ 
+
+<pre><![CDATA[
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<index xmlns="dpml:library">
+
+ <project name="demo" basedir="."/>
+
+</index>
+]]></pre>
+
+ </subsection>
+
+ <subsection name="build.xml">
+
+ 
+ The following Ant build file simply logs a message to confirm
+ that it is building. It contains a couple of empty targets
+ (clean and install) which are added simply for consistency (but
+ will be used in subsequent tutorials).
+ 
+
+<pre><![CDATA[
+<project name="demo" default="install">
+
+ <target name="clean">
+ 
+ </target>
+
+ <target name="build">
+ <echo message="Executing the simple project build."/>
+ </target>
+
+ <target name="install" depends="build"/>
+
+</project>
+]]></pre>
+
+ </subsection>
+
+ <subsection name="Building the project ..">
+
+ 
+ Assuming that you have the build file and the index file in a
+ directory and Depot is installed - you should be able to start
+ the build proces using Depot's <tt>build</tt> command as shown
+ below:
+ 
+
+ <pre>
+$ cd tutorials\tooling\simple
+$ build
+
+-------------------------------------------------------------------------
+demo#SNAPSHOT
+-------------------------------------------------------------------------
+
+build:
+ [echo] Executing the simple project build.
+
+BUILD SUCCESSFUL
+Total time: 0 seconds
+
+$
+ </pre>
+
+ </subsection>
+
+ <subsection name="Summary">
+
+ 
+ When we invoked the build command as shown above - the build tool
+ located the index.xml file (by searching from the current directory
+ up the directory tree until the file was found) and located the
+ demo project by matching the current directory with directory
resolved
+ from the project <tt>basedir</tt> attribute. Once the project
defintion
+ is located Depot constructs an internal defintion containing
information
+ about the project name, group, version, properties, filters,
+ dependency information, and information about resources that will be
+ produced by the build process.
+ 
+
+ 
+ The <a href="properties.html">next tutorial</a> introduces the
declaration
+ of project and module level properties.
+ 
+
+ </subsection>
+
+ </section>
+
+ </body>
+</document>
+

Modified: trunk/central/site/src/docs/util/transit/tutorials/repositories.xml
===================================================================
--- trunk/central/site/src/docs/util/transit/tutorials/repositories.xml
2007-03-07 03:45:30 UTC (rev 1884)
+++ trunk/central/site/src/docs/util/transit/tutorials/repositories.xml
2007-03-07 04:36:58 UTC (rev 1885)
@@ -56,29 +56,10 @@

A more typical scenario is the establishment of a company wide
repository within a
local intranet. For this you need to setup a server (e.g. HTTP)
with a file based
- resource handler then configure Transit by declaring a new remote
host and defintining
+ resource handler then configure Transit by declaring a new remote
host and definining
the host base url as the http server.


- 
- The following commandline operations demonstrate the setup of a new
local repository
- using a file protocol referencing a root repository directory of
<tt>${dpml.data}/demo</tt>.
- Symbolic expressions used within the host defintion may include any
system property and
- core Transit location references (such as <tt>${dpml.home}</tt>).
- 
-
-<pre>
-$ transit add host demo -url file:${dpml.data}/demo -priority 60
-</pre>
-
- 
- Once created the new repository can be listed using the following
command:
- 
-
-<pre>
-$ transit info
-</pre>
-
</subsection>

</section>

r1885 - in trunk/central/site/src/docs: metro/concepts util/depot/tutorials util/transit/tutorials, mcconnell at BerliOS, 03/06/2007