leosimons 2003/02/20 06:29:40
Modified: meta build.xml
meta/src/xdocs context.xml dependencies.xml extensions.xml
index.xml list.xml logging.xml pending.xml
profile.xml service.xml services.xml stages.xml
tools.xml type.xml
Added: meta/src/xdocs book.xml tabs.xml
Removed: meta/src/xdocs menu.xml
Log:
forrestize
Revision Changes Path
1.12 +1 -1 avalon-excalibur/meta/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/build.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- build.xml 6 Jan 2003 14:14:15 -0000 1.11
+++ build.xml 20 Feb 2003 14:29:39 -0000 1.12
@@ -300,7 +300,7 @@
<target name="docs" depends="xdocs,javadocs" 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="docs" description=" Places Docs ready for
hosting on website">
1.2 +5 -5 avalon-excalibur/meta/src/xdocs/context.xml
Index: context.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/context.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- context.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ context.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,13 +11,13 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.ContextDescriptor class describes the set
of context entries that a component may be depedent on. Context entries
declare a context key and the classname of the value that the component expects
to receive. A compliant container will ensure that a context object supplied
to a component under the Contextualize phase can access required context
entries with assurance that the value will be supplied under the correct key as
as an instance of the required type. The supply of optional context entries is
a container concern with the single exception that a container must ensure that
the an optional entry corresponds to the type requirested by the componet
context entry.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -59,9 +59,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.3 +5 -5 avalon-excalibur/meta/src/xdocs/dependencies.xml
Index: dependencies.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/dependencies.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- dependencies.xml 12 Nov 2002 01:20:29 -0000 1.2
+++ dependencies.xml 20 Feb 2003 14:29:39 -0000 1.3
@@ -11,12 +11,12 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.DependencyDescriptor class associates a
rol name with a version interface reference. A depedency is a references to a
service provided by a component. A container will typically provide services to
resolve service providers with components declaring depedencies by matching
provider and dependency declaration references.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -84,9 +84,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.2 +5 -5 avalon-excalibur/meta/src/xdocs/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/extensions.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- extensions.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ extensions.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,13 +11,13 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.ExtensionDescriptor class declares tha
ability of a component implementation to provide support for the handling of
another component declararing a lifecycle stage interface dependency. For
example, component A may declare that it is capable of supporting lifecycle
interface X and component B may declare that it requires a handler for
lifecycle stage interface X. A compliant container will handle the association
of a component capable of handling the the lifecycle stage interface with the
component declaring the stage dependency.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -43,9 +43,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.2 +5 -5 avalon-excalibur/meta/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ index.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,7 +11,7 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>The Meta Model is an object model describing a type of Avalon component.
The meta model encompasses all information about a component that is not
@@ -49,8 +49,8 @@
It should provide support for both linear and hierarchical metadata.
</p>
- </s1>
- <s1 title="Design Constraints">
+ </section>
+ <section><title>Design Constraints</title>
<p>The Meta Model should be restricted to the same problem domain as avalon
itself: it should be specifically about enabling COP. It should be small
@@ -60,7 +60,7 @@
<p>ECM is stable and phoenix is in beta. The meta model should provide as
much interoperability with and support for these projects as possible.</p>
- </s1>
+ </section>
</body>
1.2 +3 -3 avalon-excalibur/meta/src/xdocs/list.xml
Index: list.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/list.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- list.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ list.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -9,11 +9,11 @@
</header>
<body>
- <s1 title="Mailing Lists">
+ <section><title>Mailing Lists</title>
<p>
The Avalon Meta Model 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.2 +5 -5 avalon-excalibur/meta/src/xdocs/logging.xml
Index: logging.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/logging.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- logging.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ logging.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,13 +11,13 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.LoggerDescriptor class describes the set
of logging channels that the component requires. The name of each logging
channel is relative to the logging channel passed to the component. For
example, a component hosted in a container names aaa/bbb/ccc will be supplied
with a logging with a catagory of aaa.bbb.ccc.your-component and the logging
categories defined in the meta-info model will be appended to that (using the
period as a category delimiter).
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -48,9 +48,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.2 +3 -3 avalon-excalibur/meta/src/xdocs/pending.xml
Index: pending.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/pending.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pending.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ pending.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -9,11 +9,11 @@
</header>
<body>
- <s1 title="Unavailable">
+ <section><title>Unavailable</title>
<p>
The information you have selected is cutrrently in development. PLease
check back soon.
</p>
- </s1>
+ </section>
</body>
<footer>
1.3 +7 -7 avalon-excalibur/meta/src/xdocs/profile.xml
Index: profile.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/profile.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- profile.xml 19 Nov 2002 19:17:47 -0000 1.2
+++ profile.xml 20 Feb 2003 14:29:39 -0000 1.3
@@ -11,7 +11,7 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>A profile is the definition of the criteria for the establishment of a
component. A profile, when included within the scope of a container
declaration, will be instantiated in the model as an EXPLICIT profile resulting
in the initiation of dependency resolution relative to the component as the
target deployment objective. Multiple supplementary profiles may be packaged
in a files <classname>.xprofile. Profile declarations included within an
.xprofile resource are refered to as packaged profiles.</p>
<p>A profile represents an aggregation of the following information:</p>
@@ -28,12 +28,12 @@
<li>the parameters to be applied</li>
</ul>
-<s2 title="UML">
+<section><title>UML</title>
<p>An overview of the Profile object model is presented in the following UML
diagram.</p>
<img src="images/Profile.gif" />
-</s2>
+</section>
-<s2 title="XML">
+<section><title>XML</title>
<p>The Profile API includes factory services that support the creation of a
profile instance from an XML description. The following XML is an example of a
profile declaration.</p>
<source>
@@ -86,8 +86,8 @@
</component>
</source>
-</s2>
-</s1>
+</section>
+</section>
</body>
<footer>
1.2 +5 -5 avalon-excalibur/meta/src/xdocs/service.xml
Index: service.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- service.xml 22 Sep 2002 07:56:38 -0000 1.1
+++ service.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,7 +11,7 @@
<body>
-<s1 title="Introduction">
+<section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.ServiceDefinition class describes a type
of service. It suppliments the classic Java interface with a version identifier
and attributes. A ServiceDefintion may be referenced by multiple components
that will typically suppliment the defintion in terms of additional
attributes. References to a ServiceDefintion concern a component type
declaration of depedencies, service access points, lifestyle extension ability,
and lifestyle extension depedencies.</p>
@@ -34,7 +34,7 @@
ServiceDefinition defintion = builder.build( this.class() );
</source>
-<s2 title="XML Schema">
+<section><title>XML Schema</title>
<source>
@@ -65,9 +65,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.3 +5 -5 avalon-excalibur/meta/src/xdocs/services.xml
Index: services.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/services.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- services.xml 22 Sep 2002 07:55:15 -0000 1.2
+++ services.xml 20 Feb 2003 14:29:39 -0000 1.3
@@ -11,12 +11,12 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.ServiceDescriptor class describes a
service delivery capability. It contains a reference to ServiceDefinition.
Service delivery capability represent the value-proposition that the component
type offers to its clients. Client typically include other component that have
declared dependencies on the type of service referenced by the
ServiceDescriptor. Services supporting dependency requirements are exposed to
clients though a ServiceManager (or ComponentManager). Services supporting
lifecycle extensions are applied by a container during the startup, access and
shutdown phases. For depedent services, the client will typically invoke the
<code>lookup</code> operation against the supplied service manager, passing the
role name of the to the manager. The object retured is the service (or a proxy
that isolates the component from the offered service). Role names and the
services that the role refers to are declared in depedency entries within the
meta model.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -77,9 +77,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.2 +5 -5 avalon-excalibur/meta/src/xdocs/stages.xml
Index: stages.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/stages.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- stages.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ stages.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,7 +11,7 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
The org.apache.excalibur.meta.info.StageDescriptor class declares a
depedency that
@@ -22,7 +22,7 @@
extension candidates based on the interface reference.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<source>
@@ -56,9 +56,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.2 +9 -9 avalon-excalibur/meta/src/xdocs/tools.xml
Index: tools.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/tools.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tools.xml 25 Aug 2002 02:50:28 -0000 1.1
+++ tools.xml 20 Feb 2003 14:29:39 -0000 1.2
@@ -11,7 +11,7 @@
<body>
- <s1 title="Tools Support">
+ <section><title>Tools Support</title>
<p>Tool support can be broken up into two categories.</p>
@@ -23,16 +23,16 @@
</ul>
</p>
- <s2 title="Containers">
- </s2>
+ <section><title>Containers</title>
+ </section>
- <s2 title="Generation Tools">
- </s2>
+ <section><title>Generation Tools</title>
+ </section>
- <s2 title="Developer Tools">
- </s2>
+ <section><title>Developer Tools</title>
+ </section>
- </s1>
+ </section>
</body>
1.5 +5 -5 avalon-excalibur/meta/src/xdocs/type.xml
Index: type.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/meta/src/xdocs/type.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- type.xml 22 Sep 2002 07:55:15 -0000 1.4
+++ type.xml 20 Feb 2003 14:29:39 -0000 1.5
@@ -11,7 +11,7 @@
<body>
- <s1 title="Introduction">
+ <section><title>Introduction</title>
<p>
Type is an assembly of descriptors of the constraints a component
@@ -21,7 +21,7 @@
information about the component type.
</p>
- <s2 title="XML Schema">
+ <section><title>XML Schema</title>
<p>Configuration instances supplied to the builder shall correspond to the
<a href="http://jakarta.apache.org/avalon/dtds/meta/type-1_1.dtd";>type DTD</a>.
The structure of a Type XML document is is described below:</p>
@@ -191,9 +191,9 @@
</source>
- </s2>
+ </section>
- </s1>
+ </section>
</body>
1.1 avalon-excalibur/meta/src/xdocs/book.xml
Index: book.xml
===================================================================
<book software="Excalibur meta" title="Excalibur meta" copyright="@year@ The
Apache Software Foundation" xmlns:xlink="http://www.w3.org/1999/xlink";>
<logo href="images/merlin_logo.gif">Merlin</logo>
<menu label="Essentials">
<menu-item label="Overview" href="index.html"/>
<menu-item label="Tools" href="tools.html"/>
</menu>
<menu label="Profile">
<menu-item label="Profile Defintion" href="profile.html"/>
</menu>
<menu label="Service">
<menu-item label="Service Definition" href="service.html"/>
</menu>
<menu label="Type">
<menu-item label="Type Defintion" href="type.html"/>
<menu-item label="Logging Crieria" href="logging.html"/>
<menu-item label="Context Crieria" href="context.html"/>
<menu-item label="Services" href="services.html"/>
<menu-item label="Dependencies" href="dependencies.html"/>
<menu-item label="Extensions" href="extensions.html"/>
<menu-item label="Stages" href="stages.html"/>
</menu>
<menu label="Links">
<menu-item label="Mailing List" href="list.html"/>
<menu-item label="Merlin"
href="http://jakarta.apache.org/avalon/excalibur/merlin"/>
<menu-item label="Fortress"
href="http://jakarta.apache.org/avalon/excalibur/fortress"/>
</menu>
<menu label="Reference">
<menu-item label="API Docs" href="http://avalon.apache.org/api/"/>
</menu>
</book>
1.1 avalon-excalibur/meta/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 meta"
title="Excalibur meta"
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]
