hivemind-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From k...@apache.org
Subject svn commit: r191423 - /jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml
Date Mon, 20 Jun 2005 08:46:36 GMT
Author: knut
Date: Mon Jun 20 01:46:35 2005
New Revision: 191423

URL: http://svn.apache.org/viewcvs?rev=191423&view=rev
Log:
Replaced references to Apache Avalon with references to 
subproject Apache Excalibur, as Avalon has closed. Fixes 
HIVEMIND-133.

Modified:
    jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml

Modified: jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml
URL: http://svn.apache.org/viewcvs/jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml?rev=191423&r1=191422&r2=191423&view=diff
==============================================================================
--- jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml (original)
+++ jakarta/hivemind/trunk/src/documentation/content/xdocs/ioc.xml Mon Jun 20 01:46:35 2005
@@ -26,12 +26,12 @@
 	</header>
 	<body>
 		<p>Seems like <fork
-			href="http://avalon.apache.org/framework/guide-patterns-ioc.html"><strong>
+			href="http://excalibur.apache.org/framework/guide-patterns-ioc.html"><strong>
 			Inversion of Control</strong></fork> is all the rage these days. The <fork
-			href="http://avalon.apache.org/">Avalon</fork> project is completely based
-			around it. Avalon uses detailed assembly descriptions to tie services
-			together ... there's no way an Avalon component can "look up" another
-			component; in Avalon you explicitly connect services together.</p>
+			href="http://excalibur.apache.org/">Apache Excalibur</fork> project is completely
based
+			around it. Excalibur uses detailed assembly descriptions to tie services
+			together ... there's no way an Excalibur component can "look up" another
+			component; in Excalibur you explicitly connect services together.</p>
 		<p>That's the basic concept of Inversion of Control; you don't create your
 			objects, you describe how they should be created. You don't directly
 			connect your components and services together in code, you describe which
@@ -49,7 +49,7 @@
 				<td>Services need to implement a dedicated interface through which they
 					are provided with an object from which they can look up dependencies
 					(other services). This is the pattern used by the earlier containers
-					provided by Avalon.</td>
+					provided by Excalibur.</td>
 			</tr>
 			<tr>
 				<td>type-2</td>
@@ -65,7 +65,7 @@
 					PicoContainer</fork>, and is also used in HiveMind and Spring.</td>
 			</tr>
 		</table>
-		<p>HiveMind is a much looser system than Avalon. HiveMind doesn't have an
+		<p>HiveMind is a much looser system than Excalibur. HiveMind doesn't have an
 			explicit assembly stage; it wires together all the modules it can find at
 			runtime. HiveMind is responsible for creating services (including core
 			implementations and interceptors). It is quite possible to create service
@@ -81,13 +81,13 @@
 			You only need to provide a setter method. The properties are properties of
 			the core service implementation, there is no need for the accessor methods
 			to be part of the service interface.</p>
-		<p>HiveMind's lifecycle support is much more rudimentary than Avalon's. Your
+		<p>HiveMind's lifecycle support is much more rudimentary than Excalibur's. Your
 			service implementations can get hivemindcallbacks when they are first
 			created, and when they are discarded, by implementing certain interfaces.</p>
-		<p>Purist inversion of control, as in Avalon, may be more appropriate in
+		<p>Purist inversion of control, as in Excalibur, may be more appropriate in
 			well-constrained systems containing untrusted code. HiveMind is a layer
 			below that, not an application server, but a microkernel. Although I can
 			see using HiveMind as the infrastructure of an application server, even an
-			Avalon application server, it doesn't directly overlap otherwise.</p>
+			Excalibur application server, it doesn't directly overlap otherwise.</p>
 	</body>
 </document>



---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org


Mime
View raw message