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/10/29 18:01:30 UTC
cvs commit: avalon-excalibur/site/xdocs component.xml index.xml navigation.xml
mcconnell 2003/10/29 09:01:30
Modified: site/xdocs index.xml navigation.xml
Added: site/xdocs component.xml
Log:
Add local ECM page.
Revision Changes Path
1.3 +1 -1 avalon-excalibur/site/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/site/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 28 Oct 2003 23:25:31 -0000 1.2
+++ index.xml 29 Oct 2003 17:01:30 -0000 1.3
@@ -163,7 +163,7 @@
</p>
</td>
</tr>
- <tr><td>Component</td><td>
+ <tr><td><a href="component.html">Component</a></td><td>
<p>
Due to a number of issues in ECM, not the least of which is a
simplistic and convoluted design, it has been deprecated in
1.3 +5 -1 avalon-excalibur/site/xdocs/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/avalon-excalibur/site/xdocs/navigation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- navigation.xml 29 Oct 2003 14:51:43 -0000 1.2
+++ navigation.xml 29 Oct 2003 17:01:30 -0000 1.3
@@ -14,7 +14,11 @@
</links>
<menu name="About Excalibur">
- <item name="Overview" href="/index.html"/>
+ <item name="Overview" href="/index.html">
+ <item name="Configuration" href="configuration/index.html"/>
+ <item name="I18N" href="i18n/index.html"/>
+ <item name="ECM" href="component.html"/>
+ </item>
<item name="Download" href="http://avalon.apache.org/download.cgi"/>
<item name="Where's my documentation???" href="/no-docs-available.html"/>
<item name="Javadocs" href="http://avalon.apache.org/excalibur/api/"/>
1.1 avalon-excalibur/site/xdocs/component.xml
Index: component.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<author email="dev@avalon.apache.org">Avalon Documentation Team</author>
<title>Excalibur i18n</title>
</properties>
<body>
<section name="Excalibur ECM (DEPRICATED)">
<p>
Due to a number of issues in ECM, not the least of which is a
simplistic and convoluted design, it has been deprecated in
favor of Fortress or Phoenix. Fortress has been designed with
ECM users in mind, so it provides a number of goodies to make
it easier to migrate forward. This project will be maintained
for bug fixes only.
</p>
<subsection name="Introduction">
<p>
This project contains utilities for managing components. ECM
is what we call an "avalon container", though it is somewhat
different in architecture to newer developments like phoenix
and fortress. Our intend is to someday completely replace ECM
with fortress.
In particular, this package contains the
ExcaliburComponentManager, usually abbreviated to ECM.
</p>
</subsection>
<subsection name="Automated Component Management">
<p>
The <code>org.apache.avalon.excalibur.component</code> package
in Excalibur will allow you to manage components specified in
a configuration file. The beauty of this approach is that the
ComponentManagers and ComponentSelectors become the Container
and automagically maintain your Component's lifecycle.
</p>
<p>
The Excalibur Component Management infrastructure uses a
RoleManager to help your configuration files remain readable.
All classes are instantiated using the current thread's
ContextClassLoader--unless you pass a different one in the
constructor.
</p>
</subsection>
<subsection name="The Developing with Avalon paper">
<p>
ECM is well-documented in the Developing with Avalon
whitepaper available
<a href="http://avalon.apache.org/developing/">here</a>.
</p>
</subsection>
</section>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org