You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by mc...@apache.org on 2003/07/22 08:03:50 UTC
cvs commit: avalon-sandbox/meta/site/xdocs/tools index.xml
mcconnell 2003/07/21 23:03:49
Modified: meta/site/xdocs index.xml
meta/site/xdocs/meta index.xml
meta/site/xdocs/meta/data index.xml
meta/site/xdocs/meta/info index.xml
meta/site/xdocs/meta/info/attributes index.xml
meta/site/xdocs/meta/info/type index.xml
meta/site/xdocs/tools index.xml
Log:
Spelling updates.
Revision Changes Path
1.2 +4 -6 avalon-sandbox/meta/site/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 14 Jul 2003 20:22:18 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -13,7 +13,7 @@
<subsection name="Meta Model Overview">
<p>
- The Avalon Meta Model defines the fuctional structure
+ The Avalon Meta Model defines the functional structure
of component types and services. A Type definition contains
information about deployment and runtime dependencies together
with information about the services that a
@@ -27,7 +27,7 @@
Avalon provides a set of tools that automate the process
of generating meta-info descriptors. These tools provide
support for the generation of serializable and XML based
- descriptors that are colocated with class files. Tool
+ descriptors that are collocated with class files. Tool
support is available for Ant and Maven.
</p>
</subsection>
@@ -37,8 +37,8 @@
Type and service meta models are established as
immutable objects that complement the classic information
available about a class. Using the Type and Service
- descriptor classes, developers can are assured of greater
- portability and ieroperability of container-side applications.
+ descriptor classes, developers can be assured of greater
+ portability and interoperability of container-side applications.
</p>
</subsection>
@@ -47,5 +47,3 @@
</body>
</document>
-
-
1.2 +2 -4 avalon-sandbox/meta/site/xdocs/meta/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/meta/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 14 Jul 2003 20:22:18 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -28,8 +28,8 @@
The meta model encompasses all information about a component that is not
specified by its work interface and/or lifecycle interfaces.
Specifically, the Meta Model allows for specification of
-lifecycle-related constraints/requirments, ie Context, Configuration,
-Parameter, and Dependency constraints/requirments.
+lifecycle-related constraints/requirements, i.e. Context, Configuration,
+Parameter, and Dependency constraints/requirements.
</p>
<p>
The Meta Model API is a set of well-known interfaces and classes that
@@ -48,5 +48,3 @@
</body>
</document>
-
-
1.2 +26 -2 avalon-sandbox/meta/site/xdocs/meta/data/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/meta/data/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 15 Jul 2003 23:40:42 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -12,12 +12,36 @@
<section name="Meta Data">
<subsection name="Overview">
- <p>IN PREPARATION</p>
+ <p>Meta-info establishes functional and operational
+ constraints whereas meta-data describes data that is
+ used to fulfil those constraints. For example we may
+ have a meta-info object that describes a component type together
+ some specific context requirements. A corresponding
+ meta-data object would describe how those requirement are
+ fulfilled. Generally speaking, meta-info is referred to
+ as a descriptor whereas meta-data is referred to as a
+ directive. One describes a constraint - the other fulfils
+ the constraint.</p>
</subsection>
+ <subsection name="Status">
+ <p>The meta-model presented here addresses the meta-info
+ aspects - itself crucial to the overall objective of establishing
+ a common component criteria definition. Within Avalon there are
+ several contains each using a container specific meta-data models.
+ The objective of an Avalon Meta-Data framework is to enable a
+ common XML schema and supporting API to represent the deployment
+ information. A common meta-data model has not been established
+ at this time - however, the benefits are obvious. More
+ significantly a common meta-data model will enable intelligent
+ automation of many component management aspects in a container
+ independent fashion. For additional information please post
+ questions to the <a href="mailto:dev@avalon.apache.org">Avalon dev
+ mailing list</a>.
+ </subsection>
+
</section>
</body>
</document>
-
1.2 +3 -5 avalon-sandbox/meta/site/xdocs/meta/info/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/meta/info/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 14 Jul 2003 20:22:18 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -20,7 +20,7 @@
Definition of the component type. A Type meta info object
describes the structural features of component at the level
equivalent to a class. A type includes information about
- deployment and runtime depedencies together arbitary attributes,
+ deployment and runtime dependencies together arbitrary attributes,
a component implementation version and a component type name.
</td>
</tr>
@@ -29,13 +29,13 @@
<td>
A service is a meta info object that describes a service
provided by a component type. Service support the attribution
- of a version and arbitary properties.</td>
+ of a version and arbitrary properties.</td>
</tr>
<tr>
<td><a href="attributes/index.html">Attributes</a></td>
<td>
Attribute declarations using in conjunction with meta-info
- directives suppporting customization of the meta-info model.
+ descriptors supporting customisation of the meta-info model.
</td>
</tr>
</table>
@@ -43,5 +43,3 @@
</body>
</document>
-
-
1.2 +2 -3 avalon-sandbox/meta/site/xdocs/meta/info/attributes/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/meta/info/attributes/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 14 Jul 2003 20:22:18 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -15,7 +15,7 @@
<tr>
<td><a href="attribute.html">attribute</a></td><td>0..n</td>
<td>
- An attribute declartation.
+ An attribute declaration.
</td>
</tr>
</table>
@@ -50,5 +50,4 @@
</footer>
</document>
-
1.2 +14 -16 avalon-sandbox/meta/site/xdocs/meta/info/type/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/meta/info/type/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 14 Jul 2003 20:22:18 -0000 1.1
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.2
@@ -57,7 +57,7 @@
<tr>
<td><a href="extensions/index.html">extensions</a></td><td>0..1</td>
<td>
- Declaration of the set of deployment stage handling abiliites that
+ Declaration of the set of deployment stage handling abilities that
this component type can provide.
</td>
</tr>
@@ -78,7 +78,7 @@
<subsection name="Example XML">
<p>Configuration instances supplied to the builder shall correspond to the <a href="http://avalon.apache.org/dtds/meta/type_1_1.dtd">type DTD</a>.
-The structure of a Type XML document is is described below:</p>
+The structure of a Type XML document is described below:</p>
<source>
@@ -135,7 +135,7 @@
<font color="gray"><i><!--
Declaration of the context constraints for the compoent type.
The "type" attribute is the name of an interface derived from the default
- contenxt interface org.apache.avalon.framework.context.Context
+ context interface org.apache.avalon.framework.context.Context
--></i></font>
<context type="<font color="darkred">MyContextInterface</font>">
@@ -144,7 +144,7 @@
Declaration of an entry in a context object, the "key" is
the key used by a component to locate the context entry,
the "type" is the classname of value (typically an interface)
- or primative type. The default value is java.lang.String.
+ or primitive type. The default value is java.lang.String.
The "optional" attribute is a boolean value derived from the
TRUE or FALSE that indicates if the context value must be
provided or not (default is FALSE).
@@ -157,9 +157,9 @@
<font color="gray"><i><!--
Declaration of the set of services that this component is capable
- of supplying. Each service declarared under the services element
+ of supplying. Each service declared under the services element
may be referenced by other component info descriptions as a
- dependecy. A container is responsible for the assemably of
+ dependency. A container is responsible for the assembly of
components based on the connection of supply components to
consumer components via a common service description.
--></i></font>
@@ -168,7 +168,7 @@
<font color="gray"><i><!--
The service element declares the classname of an service
- interface and the version identifier the qualifes the service
+ interface and the version identifier the qualifies the service
version. The default version value is 1.0.
--></i></font>
@@ -180,7 +180,7 @@
<font color="gray"><i><!--
Attributes qualifying a service implementation may be included
- as supplimentary information to the attributes declared under
+ as supplementary information to the attributes declared under
a ServiceDefintion.
--></i></font>
@@ -192,10 +192,10 @@
<font color="gray"><i><!--
- Declaration of the set of dependecies that this component type has on
+ Declaration of the set of dependencies that this component type has on
component suppliers. Dependency declarations define the role name
that the component will use to access a service via a service
- or component manager. A dependecy may be declared as optional by
+ or component manager. A dependency may be declared as optional by
setting the optional attribute value to TRUE. The default value
for optional is FALSE.
--></i></font>
@@ -205,7 +205,7 @@
<font color="gray"><i><!--
A dependency declaration. In the following example the optional
attribute is redundant as it is equivalent to the default value
- but is included here for completness.
+ but is included here for completeness.
--></i></font>
<dependency optional="<font color="darkred">FALSE</font>"
@@ -242,11 +242,9 @@
<footer>
<legal>
- Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
+ Copyright (c) @year@ The Avalon Apache Project All rights reserved.
$Revision$ $Date$
</legal>
</footer>
-</document>
-
-
+</document>
\ No newline at end of file
1.3 +5 -6 avalon-sandbox/meta/site/xdocs/tools/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-sandbox/meta/site/xdocs/tools/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 15 Jul 2003 23:55:15 -0000 1.2
+++ index.xml 22 Jul 2003 06:03:49 -0000 1.3
@@ -13,8 +13,8 @@
<p>
The Avalon platform includes a set of developer tools that assist in the automation
-of different process contributing to reliable and consistant component development.
-These tools include an Ant task supporting meta info generation for component types
+of different process contributing to reliable and consistent component development.
+These tools include an Ant task supporting meta-info generation for component types
and services, and an equivalent Maven plugin.
</p>
<subsection name="Index">
@@ -24,7 +24,8 @@
<td><a href="tags/index.html">Javadoc Tags</a></td>
<td>
Reference specification of the Javadoc Tags used to
- support automation of component and service metadata.
+ support automation of component and service meta info
+ generation.
</td>
</tr>
<tr>
@@ -38,7 +39,7 @@
<td><a href="maven/index.html">Maven Plugin</a></td>
<td>
The Avalon plugin for Maven provides support for
- meta infor generation when building with the Maven tool.
+ meta info generation when building with the Maven tool.
</td>
</tr>
</table>
@@ -48,5 +49,3 @@
</body>
</document>
-
-
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org