You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hivemind.apache.org by kn...@apache.org on 2005/04/27 10:13:30 UTC
cvs commit: jakarta-hivemind/src/documentation/content/xdocs bootstrap.xml
knut 2005/04/27 01:13:30
Modified: src/documentation/content/xdocs bootstrap.xml
Log:
fixed some typos (thanks to Mike Jones)
Revision Changes Path
1.14 +9 -9 jakarta-hivemind/src/documentation/content/xdocs/bootstrap.xml
Index: bootstrap.xml
===================================================================
RCS file: /home/cvs/jakarta-hivemind/src/documentation/content/xdocs/bootstrap.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- bootstrap.xml 10 Feb 2005 01:04:34 -0000 1.13
+++ bootstrap.xml 27 Apr 2005 08:13:30 -0000 1.14
@@ -70,8 +70,7 @@
<p>
The example includes three additional interfaces and matching implementations:
- for a Subtracter, Multiplier, Divider, and lastly, a Calculator that combines them
- together:
+ for a Subtracter, Multiplier, Divider, and lastly, a Calculator that combines them:
</p>
<source><![CDATA[
@@ -85,7 +84,7 @@
<p>
The Calculator implementation will require some wiring; it expects that each of the other four
-services (Adder, Substracter, Multiplier and Divider) will be plugged into it:
+services (Adder, Subtracter, Multiplier and Divider) will be plugged into it:
</p>
<source><![CDATA[
@@ -171,7 +170,7 @@
<interceptor service-id="hivemind.LoggingInterceptor"/>
</service-point>
- <service-point id="Multiplier" interface="Multipler">
+ <service-point id="Multiplier" interface="Multiplier">
<create-instance class="impl.MultiplierImpl"/>
<interceptor service-id="hivemind.LoggingInterceptor"/>
</service-point>
@@ -184,24 +183,25 @@
<service-point id="Calculator" interface="Calculator">
<invoke-factory>
<!-- Autowires service properties based on interface! -->
- <constuct class="impl.CalculatorImpl"/>
+ <construct class="impl.CalculatorImpl"/>
</invoke-factory>
<interceptor service-id="hivemind.LoggingInterceptor"/>
- </service-point>
+ </service-point>
</module>]]></source>
<p>Here we've chosen to have the module id, <code>hivemind.examples</code>,
match the package name but that is not an absolute requirement.</p>
<p>
- The interesting part is the use of the &hivemind.BuilderFactory; to construct
- the Calculator service and connect it to the other four services.
+ The interesting part is the use of the &hivemind.BuilderFactory; (through
+ &invoke-factory;) to construct the Calculator service and connect it to the
+ other four services.
</p>
</section>
<section>
<title>Building the Registry</title>
<p>Before your code can access any services (or configuration points), it
- must construct the &api.Registry;. The Registry is the application's gateway into the services
+ must construct the &api.Registry;. The Registry is the application's gateway to the services
and configurations managed by HiveMind.</p>
<source><![CDATA[
package hivemind.examples;
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org