donaldp 2002/11/01 13:34:06
Modified: src/xdocs/framework guide-cop-in-avalon.xml
Log:
Fix up the wording.
SUbmitted By: Olaf Bergner
Revision Changes Path
1.3 +7 -6 jakarta-avalon/src/xdocs/framework/guide-cop-in-avalon.xml
Index: guide-cop-in-avalon.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon/src/xdocs/framework/guide-cop-in-avalon.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- guide-cop-in-avalon.xml 14 Jul 2002 13:42:14 -0000 1.2
+++ guide-cop-in-avalon.xml 1 Nov 2002 21:34:06 -0000 1.3
@@ -105,13 +105,13 @@
</note>
</s1>
- <s1 title="The Composable">
+ <s1 title="The Composable">
<p>
In Avalon, Composable is defined as an active entity that controls
or uses Components. Its best analogy is that of a musical composer.
The musical composer chooses what instruments (Components) by their
role in the symphony (system) and tells them which notes to play.
- </p>
+ </p>
<p>
The Avalon Composable follows the principles of Inversion of Control,
and is assigned a Component Manager. Within this section we will
@@ -156,9 +156,10 @@
equivalent to a FileStore (they do the same thing), it does not mean that
they perform the same Role. The FileStore is used to store objects to
files, and the MailSpooler is used to temporarily store messages until
- they are sent. Thus they are separate roles. Sometimes you need to
- create a new interface name that does nothing more than allow access to
- alternate roles who have the same role.
+ they are sent. Thus they are separate roles. Some containers require
+ that the interface name match the key used to lookup component. In this
+ situation it you may need to create a new interface that does nothing
+ more than extend another interface and add a new role.
</p>
</s2>
<s2 title="The Component Selector">
--
To unsubscribe, e-mail: <mailto:avalon-cvs-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@;jakarta.apache.org>
