commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsi...@apache.org
Subject cvs commit: jakarta-commons/xdocs discovery.xml
Date Mon, 16 Sep 2002 14:21:49 GMT
rsitze      2002/09/16 07:21:49

  Modified:    xdocs    discovery.xml
  Log:
  Cleanup dated material.
  
  Revision  Changes    Path
  1.4       +4 -19     jakarta-commons/xdocs/discovery.xml
  
  Index: discovery.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/xdocs/discovery.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- discovery.xml	12 Sep 2002 21:59:09 -0000	1.3
  +++ discovery.xml	16 Sep 2002 14:21:49 -0000	1.4
  @@ -14,29 +14,16 @@
   <p>The Discovery component is about discovering, or finding,
   implementations for pluggable interfaces.
   Pluggable interfaces are specified with the intent that
  -multiple implementations are, or will be,
  +at least one implementation will be
   available to provide the service described by the interface.
  -Discovery provides facilities for finding and intantiating classes,
  -and for lifecycle management of singleton (factory) classes.
   </p>
   
   <p>
  -In the absence of a common service for discoverying interface
  -implementations, many components have pioneered design and
  -implementation principles for self-discovery
  +In the absence of a common service for discoverying interface implementations,
  +many components have pioneered design and implementation principles for self-discovery
   (i.e. JAXP, commons-logging, others).
   The Commons Discovery component seeks to stand on the shoulders
  -of it's predecessors by extracting the essential principles and
  -making them available to both end user developers and to facilitate
  -self-discovery for those components that would provide such services
  -through their own APIs.
  -</p>
  -
  -<p>
  -The Commons Discovery Component improves over previous implementations
  -by establishing facilities for working within managed environments.
  -These allow configuration and property overrides without appealing
  -to the global System properties (which are scoped across an entire JVM).
  +of these predecessors by identifying these basic patterns.
   </p>
   
   
  @@ -62,7 +49,6 @@
   
   </section>
   
  -<!--
   <section name="Releases">
   
   <ul>
  @@ -71,7 +57,6 @@
   </ul>
   
   </section>
  --->
   
   
   </body>
  
  
  

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message