hammant 2002/10/27 05:18:20
Modified: docs/framework guide-patterns-ioc.html
Log:
Component becomes component
Revision Changes Path
1.5 +4 -4 jakarta-avalon-site/docs/framework/guide-patterns-ioc.html
Index: guide-patterns-ioc.html
===================================================================
RCS file: /home/cvs/jakarta-avalon-site/docs/framework/guide-patterns-ioc.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- guide-patterns-ioc.html 12 Oct 2002 12:10:22 -0000 1.4
+++ guide-patterns-ioc.html 27 Oct 2002 13:18:20 -0000 1.5
@@ -50,10 +50,10 @@
of Control</i>. 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>
@@ -73,12 +73,12 @@
<div class="h3"><h3>How to Apply It</h3></div>
<p>
<i>Inversion of Control</i> is applied in a very simple
- manner. Basically, it means that the Component architecture
+ manner. Basically, it means that the component architecture
employs a <i>passive</i> structure. See the following code:
</p>
<pre>
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>
