leosimons 2003/02/20 07:53:28
Modified: container build.xml
container/src/xdocs attributes.xml extension.xml index.xml
list.xml
Added: container/src/xdocs book.xml tabs.xml
Removed: container/src/xdocs menu.xml
Log:
forrestize
Revision Changes Path
1.9 +1 -1 avalon-excalibur/container/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/container/build.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- build.xml 29 Jan 2003 14:07:38 -0000 1.8
+++ build.xml 20 Feb 2003 15:53:28 -0000 1.9
@@ -294,7 +294,7 @@
<target name="docs" depends="javadocs, xdocs" description="generates all
the Avalon documentation"/>
<target name="xdocs" description="generates the xdocs-based
documentation">
- <ant antfile="${basedir}/../cocoonbuild.xml"/>
+ <ant antfile="${basedir}/../forrestbuild.xml"/>
</target>
<target name="site" depends="xdocs" description=" Places Docs ready for
hosting on website">
1.4 +7 -7 avalon-excalibur/container/src/xdocs/attributes.xml
Index: attributes.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/container/src/xdocs/attributes.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- attributes.xml 29 Aug 2002 11:16:57 -0000 1.3
+++ attributes.xml 20 Feb 2003 15:53:28 -0000 1.4
@@ -11,7 +11,7 @@
<body>
- <s1 title="Overview">
+ <section><title>Overview</title>
<p>Within Avalon there are a number of different containers with
varying level of
consistency with respect to the naming of context keys and more
recently the subject
@@ -20,9 +20,9 @@
<p>This information should be considered as a proposal only.</p>
- </s1>
+ </section>
- <s1 title="Context Keys">
+ <section><title>Context Keys</title>
<p>The following context keys and associated values are considered to
be
applicable to all containers.</p>
@@ -64,9 +64,9 @@
</td>
</tr>
</table>
- </s1>
+ </section>
- <s1 title="Type Attributes">
+ <section><title>Type Attributes</title>
<p>The following attributes may be declared within the scope of the
component info block of the meta-info model.</p>
@@ -110,7 +110,7 @@
</tr>
</table>
- </s1>
+ </section>
</body>
1.7 +37 -37 avalon-excalibur/container/src/xdocs/extension.xml
Index: extension.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/container/src/xdocs/extension.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- extension.xml 7 Feb 2003 16:07:33 -0000 1.6
+++ extension.xml 20 Feb 2003 15:53:28 -0000 1.7
@@ -11,7 +11,7 @@
</header>
<body>
- <s1 title="What are lifecycle extensions ?">
+ <section><title>What are lifecycle extensions ?</title>
<p>
Lifecycle extensions are additional stages a component can traverse
through during
it's lifetime. Lifecycle extensions allow a container to provide extra
functionality
@@ -76,9 +76,9 @@
one of these containers and would like to use lifecycle extensions.
</p>
- </s1>
+ </section>
- <s1 title="How do I extend a Component's lifecycle ?">
+ <section><title>How do I extend a Component's lifecycle ?</title>
<p>
Extending a Component's lifecycle is straightforward. An overview of the
process
follows:
@@ -125,9 +125,9 @@
phases defined later in this document.
</p>
</ol>
- </s1>
+ </section>
- <s1 title="When can a Component's lifecycle be extended ?">
+ <section><title>When can a Component's lifecycle be extended ?</title>
<p>
The life of any component can be broken down to the following phases:
</p>
@@ -183,9 +183,9 @@
to any one context of use.
</p>
- </s1>
+ </section>
- <s1 title="Lifestyle Extension Interfaces">
+ <section><title>Lifestyle Extension Interfaces</title>
<p>
A container manages extensions using an extension handler. Handlers
may implement
@@ -194,7 +194,7 @@
accessor extension will be activated during the access and release
stages.
</p>
- <s2 title="The Creator Interface">
+ <section><title>The Creator Interface</title>
<p>The <code>Creator</code> interface describes the create and destroy
stages that occur between a component and a container
@@ -230,9 +230,9 @@
}
</source>
- </s2>
+ </section>
- <s2 title="Accessor Interface">
+ <section><title>Accessor Interface</title>
<p>
The <code>Accessor</code> interface describes the access and release
stages that occur between a service or component manager and a container
@@ -268,10 +268,10 @@
}
</source>
- </s2>
- </s1>
+ </section>
+ </section>
- <s1 title="Fortress Example">
+ <section><title>Fortress Example</title>
<p>
Let's look at a simple example. The following is also available as a
working sample
@@ -283,7 +283,7 @@
Components. We'll call it the <code>SecurityManageable</code> interface.
</p>
- <s2 title="Define the component extension interface">
+ <section><title>Define the component extension interface</title>
<p>
First we define the new Component extension interface.
@@ -306,9 +306,9 @@
}
</source>
- </s2>
+ </section>
- <s2 title="Create the lifecycle extensions class">
+ <section><title>Create the lifecycle extensions class</title>
<p>
Next we define the actual extension implementation which invokes the
<code>secure()</code>
@@ -351,9 +351,9 @@
extensions, and are not limited to just one.</note>
</p>
- </s2>
+ </section>
- <s2 title="Register the lifecycle extensions class">
+ <section><title>Register the lifecycle extensions class</title>
<p>
We then inform our container about the extension. This could be done in
several different
@@ -384,9 +384,9 @@
}
</source>
- </s2>
+ </section>
- <s2 title="Use the new component interface">
+ <section><title>Use the new component interface</title>
<p>
To use the new SecurityManageable lifecycle extension, we simply
implement
@@ -432,13 +432,13 @@
}
}
</source>
- </s2>
+ </section>
- </s1>
+ </section>
- <s1 title="Merlin Example">
+ <section><title>Merlin Example</title>
- <s2 title="Create your lifestyle stage interface">
+ <section><title>Create your lifestyle stage interface</title>
<p>
The following interface is your domain specific lifecycle stage interface.
It is the interface that an extension handler will use to interact with your
component during deployment and decommissioning.
@@ -455,9 +455,9 @@
}
</source>
- </s2>
+ </section>
- <s2 title="Create the lifestyle extension handler">
+ <section><title>Create the lifestyle extension handler</title>
<p>
An extension handler is the implementation class that will be activated by
the Merlin container to handle domain specific tasks during the deployment and
decommissioning phases. The extension can implement etier or both of the
Creator and Accessor interfaces depeding on the particular extension
requirements. IN this example we are defining a simple creation stage handler
that supplies a message to an instance of Exploitable.
@@ -513,9 +513,9 @@
</source>
- </s2>
+ </section>
- <s2 title="Create a component implementing the stage interface">
+ <section><title>Create a component implementing the stage
interface</title>
<source>
public class MyComponent extends AbstractLogEnabled implements Exploitable
{
@@ -551,9 +551,9 @@
</type>
</source>
- </s2>
+ </section>
- <s2 title="Register you component and the extension">
+ <section><title>Register you component and the extension</title>
<p>To complete the process you need to declare your handler and component in
a jar manifest file. The following entries show the declaration of the
component and the extension handler.</p>
@@ -568,9 +568,9 @@
Avalon: Type
</source>
- </s2>
+ </section>
- <s2 title="Execute the example">
+ <section><title>Execute the example</title>
<p>To execute the example you simply need to include a reference to you
component within a Merlin container declaration. The following XML source
declares a Merlin kernel, container, and component. You don't need to include
the handler because Merlin can sort that out itself based on the information
supplied in the meta-info declarations.</p>
@@ -592,16 +592,16 @@
</kernel>
</source>
- </s2>
+ </section>
- </s1>
+ </section>
- <s1 title="Need more information ?">
+ <section><title>Need more information ?</title>
<p>
If you have any particular questions, comments, etc, please send an
email to the Avalon
developer mailing <link href="mailto:dev@avalon.apache.org";>list</link>.
</p>
- </s1>
+ </section>
</body>
<footer>
1.6 +36 -17 avalon-excalibur/container/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/container/src/xdocs/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 29 Aug 2002 11:16:57 -0000 1.5
+++ index.xml 20 Feb 2003 15:53:28 -0000 1.6
@@ -11,24 +11,43 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
- <p>The Excalibur Container package has been established as repository
of interfaces, classes, and documentation pertaining to open, portable
container development for the Avalon Component Model.</p>
+ <p>The Excalibur Container package has been established as
+ repository of interfaces, classes, and documentation pertaining
+ to open, portable container development for the Avalon Component
+ Model.</p>
+
+ <p>Contributions to this project are based on co-development actives
+ by container projects aiming towards cross-container component
+ portability and consistent service management.</p>
+
+ <section><title>Lifestyle Extensions</title>
+
+ <p>The first step in the container project has been undertaken
+ between the Fortress and Merlin containers on the subject of
+ lifestyle extension support. The original design and
+ implementation of lifecycle extensions by Marcus Crafter was
+ implemented using the Fortress container. Subsequently, and
+ alternative implementation based on Marcus' design was
+ introduced using the Merlin container leading to two
+ incompatible solutions aiming at the same objective. Through a
+ process of cross-project collaboration, the Fortress and Merlin
+ developers reached consensus on a common set of APIs and abstract
+ implementation. These resources constitute the first sub-project
+ of the Excalibur Container package.</p>
+
+ </section>
+
+ <section><title>Attributes</title>
+
+ <p>The attributes activity deals with the proposed
+ specification of Avalon level attributes and context keys
+ and associated semantics - facilitating the portability of
+ components across different Avalon containers.</p>
+ </section>
- <p>Contributions to this project are based on co-development actives
by container projects aiming towards cross-container component portability and
consistent service management.</p>
-
- <s2 title="Lifestyle Extensions">
-
- <p>The first step in the container project has been undertaken
between the Fortress and Merlin containers on the subject of lifestyle
extension support. The original design and implementation of lifecycle
extensions by Marcus Crafter was implemented using the Fortress container.
Subsequently, and alternative implementation based on Marcus' design was
introduced using the Merlin container leading to two incompatible solutions
aiming at the same objective. Through a process of cross-project
collaboration, the Fortress and Merlin developers reached consensus on a common
set of APIs and abstract implementation. These resources constitute the first
sub-project of the Excalibur Container package.</p>
-
- </s2>
-
- <s2 title="Attributes">
-
- <p>The attributes activity deals with the proposed specification of
Avalon level attributes and context keys and associated semantics -
facilitating the portability of components across different Avalon
containers.</p>
- </s2>
-
- </s1>
+ </section>
</body>
1.2 +3 -3 avalon-excalibur/container/src/xdocs/list.xml
Index: list.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/container/src/xdocs/list.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- list.xml 24 Aug 2002 11:47:30 -0000 1.1
+++ list.xml 20 Feb 2003 15:53:28 -0000 1.2
@@ -9,11 +9,11 @@
</header>
<body>
- <s1 title="Mailing Lists">
+ <section><title>Mailing Lists</title>
<p>
The Excalibur Container project is part of the Apache Avalon Project. The <a
href="http://jakarta.apache.org/site/mail2.html#Avalon";>Avalon User list</a> is
available for general questions and queries relating to Avalon initiatives.
</p>
- </s1>
+ </section>
</body>
<footer>
1.3 +17 -12 avalon-excalibur/container/src/xdocs/book.xml
1.1 avalon-excalibur/container/src/xdocs/tabs.xml
Index: tabs.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab
V1.0//EN" "tab-cocoon-v10.dtd">
<tabs software="Excalibur container"
title="Excalibur container"
copyright="Foo"
xmlns:xlink="http://www.w3.org/1999/xlink";>
<tab label="Avalon Home" href="http://avalon.apache.org/"/>
<tab label="Framework" href="http://avalon.apache.org/framework/"/>
<tab label="Components" href="http://avalon.apache.org/components/"/>
<tab label="Phoenix" href="http://avalon.apache.org/phoenix/"/>
<tab label="SECA" href="http://avalon.apache.org/seca/"/>
<tab label="Apps" href="http://avalon.apache.org/apps/"/>
</tabs>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
