mcconnell 2002/07/06 22:02:21
Modified: assembly README.TXT
Log:
clean-up of the readme
Revision Changes Path
1.7 +7 -10 jakarta-avalon-excalibur/assembly/README.TXT
Index: README.TXT
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/assembly/README.TXT,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- README.TXT 7 Jul 2002 04:52:06 -0000 1.6
+++ README.TXT 7 Jul 2002 05:02:21 -0000 1.7
@@ -1,12 +1,10 @@
-Assembly – an open service managemet architecture.
+Merlin2 – an open service management architecture.
==================================================
-This package contains work in progress originating from the Merlin container. It
includes a set of service based on the containerkit abstraction dealing with the
defintion of a system kernel, container hierachies, component assembly, and component
deployment and decommissioning. Everything is this package is ALPHA and is subject to
changes and restructuring arising from changes in the containerkit package and general
evolution of the Assembly packages.
+This package contains work in progress originating from the Merlin container. It
includes a set of dealing with the definition of a system kernel, container
hierarchies, component assembly, and component deployment and decommissioning.
Everything is this package is ALPHA and is subject to change. A demonstration of
current status is normally possible by invoking the following ant targets:
-A demonstration of current status is normally possible by invoking the following
ant targets:
-
- ant dist
+ ant all
ant kernel
This will cause the build of the kernel, container framework, type repository, a
set of demo components, and the creation and deployment of a root container holding a
combination of component providers and subsidiary containers.
@@ -15,22 +13,21 @@
------
07-JUL-2002.
-Added support for the resolution of dependency solutions using the container
hierachy.
-Forked a sub-set of the containerkit model to provide support for more dynamic
style resolution of association at the metadata level. Improved API and class naming.
Expanded complexity of the test case (component declarations across multiple
containers, cross container depeendecy resolution, and resolution of conflicting
candidate supplier components).
+Added support for the resolution of dependency solutions using the container
hierarchy. Forked a sub-set of the containerkit model to provide support for more
dynamic style resolution of association at the meta data level. Improved API and
class naming. Expanded complexity of the test case (component declarations across
multiple containers, cross container dependency resolution, and resolution of
conflicting candidate supplier components).
03-JUL-2002.
-The initialization of the component will automatically build a component
deployment graph based on implicit dependencies and service declarations based on of
components available in the classpath, together with explict declarations including in
container configurations.
+The initialization of the component will automatically build a component deployment
graph based on implicit dependencies and service declarations based on of components
available in the classpath, together with explicit declarations including in container
configurations.
To-Do
-----
-The kernel should take advantage of Excalibur LogKit extensions (logging
configuration etc.). Functional operation of the container as a node in a container
hierachy is still very much work-in-progreess.
+The kernel should take advantage of Excalibur LogKit extensions (logging
configuration etc.). Functional operation of the container as a node in a container
hierarchy is still very much work-in-progress.
The component instantiation and lifecycle management is not included at this stage.
Before proceeding with actual component instantiation - more playing around is
required with the containerkit abstractions.
Context creation is based on the current ContextFactory class. This needs to be
updated in accordance with the specifications for context and context value creation
directives. Also, the registry needs to be updated to provide support for the import
of container based context values (refer spec).
-Management of defaults using the CascadingConfiguration need to be included. The
original Merlin approach was to include the default configuration information inside
the .xinfo file. The approach taken here eill be to seperate default information into
a <classname>.profile document.
+Management of defaults using the CascadingConfiguration need to be included. The
original Merlin approach was to include the default configuration information inside
the .xinfo file. The approach taken here will be to separate default information into
a <classname>.xconfig for default information and a <classname>.xprofile containing
default deployment descriptors.
Introduction of component factories will be required as a complement to the
<component/> directive.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
