hlship 2005/02/22 07:36:09
Modified: src/documentation/content/xdocs override.xml
Log:
Fix errors in the service override docs.
Revision Changes Path
1.9 +2 -7
jakarta-hivemind/src/documentation/content/xdocs/override.xml
Index: override.xml
===================================================================
RCS file:
/home/cvs/jakarta-hivemind/src/documentation/content/xdocs/override.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- override.xml 10 Feb 2005 01:04:34 -0000 1.8
+++ override.xml 22 Feb 2005 15:36:09 -0000 1.9
@@ -35,9 +35,6 @@
<note>Plans are afoot to refactor <link
href="site:tapestry">Tapestry</link>
3.1 to make considerable use of HiveMind. Many of the
ideas represented in
HiveMind germinated in earlier Tapestry releases.</note>
- <p>HiveMind doesn't have an explicit mechanism for
accomplishing this ...
- that's because its reasonable to replace and wrap
existing services just
- with the mechanisms already available.</p>
<p>
In HiveMind 1.0, overriding a service required a "trick", involving
indirection
via a HiveMind symbol. This has changed in HiveMind 1.1, which
supports
@@ -96,10 +93,8 @@
</section>
<section>
<title>Step Two: Add the override</title>
- <p>In this step, we still have just the two services
... Consumer and
- Provider, but they are linked together less
explicitly, by using
- substitution symbols. The other module is not
changed at all, we simply
- add a new module, containing an &implementation; for the Provider
service:</p>
+ <p>An &implementation; element will override the
default implementation from the
+ &service-point;:</p>
<source><![CDATA[
<module id="ex.override" version="1.0.0">
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
