commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hls...@apache.org
Subject cvs commit: jakarta-commons-sandbox/hivemind/xdocs localization.xml extension-points.xml services.xml ioc.xml
Date Tue, 12 Aug 2003 20:46:30 GMT
hlship      2003/08/12 13:46:30

  Modified:    hivemind/xdocs localization.xml extension-points.xml
                        services.xml ioc.xml
  Log:
  Make some improvements to the documentation.
  
  Revision  Changes    Path
  1.6       +2 -2      jakarta-commons-sandbox/hivemind/xdocs/localization.xml
  
  Index: localization.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/hivemind/xdocs/localization.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- localization.xml	7 Aug 2003 14:08:11 -0000	1.5
  +++ localization.xml	12 Aug 2003 20:46:30 -0000	1.6
  @@ -29,7 +29,7 @@
   <p>
   Services can gain access to localized messages, as an instance
   of
  -<code>org.apache.tapestry.IMessages</code>, which includes methods
  +<a href="apidocs/org/apache/commons/hivemind/Messages.html">Messages</a>, which
includes methods
   for accessing messages and formatting messages with arguments.
   </p>	
   
  
  
  
  1.4       +4 -2      jakarta-commons-sandbox/hivemind/xdocs/extension-points.xml
  
  Index: extension-points.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/hivemind/xdocs/extension-points.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- extension-points.xml	5 Aug 2003 15:41:44 -0000	1.3
  +++ extension-points.xml	12 Aug 2003 20:46:30 -0000	1.4
  @@ -219,7 +219,9 @@
   	<li><strong>Are the any default implementations of SymbolSource?</strong>
   		
   		<p>
  -		Not yet, but I'm sure there will be.	
  +	There is now an extension point for setting "factory defaults":
  +	<a href="base-registry/hivemind.html#extension-point:hivemind.FactoryDefaults">hivemind.FactoryDefaults</a>.
Additional
  +	implementations may follow in the future.
   		</p>
   		
   		</li>	
  
  
  
  1.15      +5 -5      jakarta-commons-sandbox/hivemind/xdocs/services.xml
  
  Index: services.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/hivemind/xdocs/services.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- services.xml	12 Aug 2003 17:31:54 -0000	1.14
  +++ services.xml	12 Aug 2003 20:46:30 -0000	1.15
  @@ -83,7 +83,7 @@
   			<p>
   			Often, the factory will need some additional configuration information.
   			For example, the
  -			<a href="apidocs/org/apache/commons/hivemind/service/impl/EJBProxyFactory.html">hivemind.EJBProxyFactory</a>
  +			<a href="base-registry/hivemind.html#service:hivemind.EJBProxyFactory">hivemind.EJBProxyFactory</a>
   			service uses its parameters to identify the JNDI name of the EJB's home interface.	
   			</p>
   			
  @@ -96,7 +96,7 @@
   			
   			<p>
   			Another common service factory is the 
  -			<a href="apidocs/org/apache/commons/hivemind/service/impl/BuilderFactory.html">hivemind.BuilderFactory</a>.
  +			<a href="base-registry/hivemind.html#service:hivemind.BuilderFactory">hivemind.BuilderFactory</a>.
   			It is used to construct a service and then set properties of the service implementation
object.	
   			</p>
   							
  @@ -116,7 +116,7 @@
   					service extension point), adding the functionality of that interface.
   					For example, the
   					
  -<a href="apidocs/org/apache/commons/hivemind/service/impl/LoggingInterceptorFactory.html">hivemind.LoggingInterceptor</a>
  +<a href="base-registry/hivemind.html#service:hivemind.LoggingInterceptor">hivemind.LoggingInterceptor</a>
   					factory	creates an 
   					instance that logs entry and exit to each method.
   					</p>
  @@ -262,7 +262,7 @@
   		
   		<p>
   		As an example, you may want to replace the
  -		<a href="apidocs/org/apache/commons/hivemind/service/impl/NameLookupImpl.html">hivemind.NameLookup</a>

  +		<a href="base-registry/hivemind.html#service:hivemind.NameLookup">hivemind.NameLookup</a>

   		service, to change its JNDI configuration.
   		</p>
   			
  
  
  
  1.4       +5 -2      jakarta-commons-sandbox/hivemind/xdocs/ioc.xml
  
  Index: ioc.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/hivemind/xdocs/ioc.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ioc.xml	31 Jul 2003 21:06:24 -0000	1.3
  +++ ioc.xml	12 Aug 2003 20:46:30 -0000	1.4
  @@ -41,7 +41,10 @@
   <p>
   On the other hand, HiveMind is responsible for creating services (including core implementations
   and interceptors).  It is quite possible to create service factories that do very container-like
things,
  -including connecting services together.  	
  +including connecting services together.  For example,
  +<a href="base-registry/hivemind.html#service:hivemind.BuilderFactory">hivemind.BuilderFactory</a>

  +does just that, instantiating an object to act as the core service implementation, then
setting
  +properties of the object, some of which are references to services and configuration element
data.
   </p>
   
   <p>
  
  
  

Mime
View raw message