You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by le...@apache.org on 2003/04/16 22:59:48 UTC
cvs commit: avalon-sandbox/merlin/merlin-smp/xdocs index.xml
leosimons 2003/04/16 13:59:48
Modified: merlin/merlin-smp/xdocs index.xml
Log:
fix grammar error, and formatting.
Revision Changes Path
1.4 +89 -50 avalon-sandbox/merlin/merlin-smp/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/merlin/merlin-smp/xdocs/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml 8 Apr 2003 11:19:51 -0000 1.3
+++ index.xml 16 Apr 2003 20:59:48 -0000 1.4
@@ -2,59 +2,98 @@
<document>
- <properties>
- <author email="mcconnell@apache.org">Stephen McConnell</author>
- <title>Merlin Service Management</title>
- </properties>
+ <properties>
+ <author email="mcconnell@apache.org">Stephen McConnell</author>
+ <title>Merlin Service Management</title>
+ </properties>
+
+ <body>
+
+ <section name="Merlin Service Management">
+
+ <p>
+ <strong>Welcome to Merlin.</strong>
+ </p>
+
+ <p>
+ The Merlin project deals with the broad area of service
+ and component management. The Merlin system is a container
+ that provides comprehensive support for the management of
+ complex component-based systems. Merlin uses a component
+ meta-model to facilitate the automated assembly and
+ deployment of components.
+ </p>
+
+ <p>
+ <img src="images/cover.gif"/>
+ </p>
+
+ <subsection name="Service Management Platform (SMP)">
+ <p>
+ Merlin is a service management platform based on an
+ advanced assembly engine. Its focus is to provide
+ support for the encapsulation of a set of components
+ and services within functional blocks. Blocks enable
+ the separation of components as an implementation
+ solution from services that are established by those
+ components.
+ </p>
+
+ </subsection>
+
+ <subsection name="Assembly Framework">
+
+ <p>
+ The assembly engine is responsible for the management
+ of the deployment of services provided by a component.
+ </p>
+
+ <p>
+ Components in the framework may have dependencies on
+ services provided by other components, which in turn
+ may have dependencies of their own. In addition,
+ components can declare (as part of their meta-info)
+ particular lifecycle stages (such as initiation or
+ configuration) and the type of stage provider it needs
+ to handle that stage. So in effect, components can be
+ deployed with classic runtime dependencies together
+ with deployment dependencies (because deployment stage
+ providers are themselves components that may have their
+ own deployment and runtime dependencies).
+ </p>
+
+ <p>
+ Assembly services include ordered deployment and
+ decommissioning, and a range of "lifestyle" handlers
+ (things like thread-safe, per-thread, singleton,
+ transient, or custom policies). The package includes
+ facilities for: classloader management and cascading
+ repositories for types, templates, service definitions
+ and appliance instances (where an appliance is simply
+ an instantiation of a particular component deployment
+ scenario).
+ </p>
+ </subsection>
+
+ <subsection name="Meta Model">
+ <p>
+ The meta model used in Merlin defines the notion of a
+ component type. A Type definition contains information
+ about deployment and runtime dependencies together with
+ general attributes about the type and services the
+ component type can provide. The Type and Service notions
+ are complimented by a Profile which can be viewed as a
+ template deployment scenario. Type, Service and Profile
+ descriptions can be packaged in jars files and used as
+ the basic for automating component assembly and
+ deployment.
+ </p>
- <body>
+ </subsection>
- <section name="Merlin Service Management">
+ </section>
- <p>
-<strong>Welcome to Merlin.</strong>
- </p>
-
- <p>
-The Merlin project deals with the general area of service and component management. The Merlin system is a container that provides comprehensive support for the management of complex component based systems. Merlin uses a component meta-model to facilitate the automated assembly and deployment of components.
- </p>
-
- <p>
-<img src="images/cover.gif"/>
- </p>
-
- <subsection name="Service Management Platform (SMP)">
-<p>
-Merlin is a service management platform based on an advanced assembly engine. Its focus is to provide support for the encapsulation of a set of components and services within functional blocks. Blocks enable the separation of components as an implementation solutions from services established by respective components.
- </p>
-
- </subsection>
-
- <subsection name="Assembly Framework">
-
-<p>
-The assembly engine is responsible for the management of the deployment of services provided by a component.
-</p>
-
-<p>
-Components in the framework may have dependencies on services provided by other components, which in turn may have dependencies of their own. In addition, components can declare (as part of their meta-info) particular lifecycle stages (such as initiation or configuration) and the type of stage provider it needs to handle that stage. So in effect, components can be deployed with classic runtime dependencies together with deployment dependencies (because deployment stage providers are themselves components that may have their own deployment and runtime dependencies).
-</p>
-
-<p>
-Assembly services include ordered deployment and decommissioning, and a range of "lifestyle" handlers (things like thread-safe, per-thread, singleton, transient, or custom policies). The package includes facilities for: classloader management and cascading repositories for types, templates, service definitions and appliance instances (where an appliance is simply an instantiation of a particular component deployment scenario).
-</p>
- </subsection>
-
- <subsection name="Meta Model">
-<p>
-The meta model used in Merlin defines the notion of a component type. A Type definition contains information about deployment and runtime dependencies together with general attributes about the type and services the component type can provide. The Type and Service notions are complimented by a Profile which can be viewed as a template deployment scenario. Type, Service and Profile descriptions can be packaged in jars files and used as the basic for automating component assembly and deployment.
-</p>
-
- </subsection>
-
- </section>
-
- </body>
+ </body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org