hammant 2002/10/27 04:53:27
Modified: src/xdocs/framework guide-patterns-ioc.xml
Log:
Component becomes component
Revision Changes Path
1.2 +5 -5 jakarta-avalon/src/xdocs/framework/guide-patterns-ioc.xml
Index: guide-patterns-ioc.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon/src/xdocs/framework/guide-patterns-ioc.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- guide-patterns-ioc.xml 3 May 2002 10:19:53 -0000 1.1
+++ guide-patterns-ioc.xml 27 Oct 2002 12:53:27 -0000 1.2
@@ -52,10 +52,10 @@
of Control</em>. The military provides each new recruit
with the basic things they need to operate at their rank,
and issues commands that recruit must obey. The same
- principle applies in code. Each Component is given the
+ principle applies in code. Each component is given the
provisions they need to operate by the instantiating
entity (i.e. Commanding Officer in this analogy). The
- instantiating entity then acts on that Component how it
+ instantiating entity then acts on that component how it
needs to act.
</p>
<p>
@@ -75,12 +75,12 @@
<s1 title="How to Apply It">
<p>
<em>Inversion of Control</em> is applied in a very simple
- manner. Basically, it means that the Component architecture
+ manner. Basically, it means that the component architecture
employs a <em>passive</em> structure. See the following code:
</p>
<source>
class MyComponent
- implements Component, LogEnabled
+ implements LogEnabled
{
Logger logger;
--
To unsubscribe, e-mail: <mailto:avalon-cvs-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@;jakarta.apache.org>
