You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by pr...@apache.org on 2002/07/19 20:32:47 UTC

cvs commit: jakarta-avalon-excalibur/configuration README.txt

proyal      2002/07/19 11:32:47

  Modified:    configuration/src/xdocs index.xml menu.xml
               configuration README.txt
  Log:
  Update readme + link in new docs
  
  Revision  Changes    Path
  1.4       +22 -6     jakarta-avalon-excalibur/configuration/src/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/configuration/src/xdocs/index.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- index.xml	13 Jul 2002 18:29:04 -0000	1.3
  +++ index.xml	19 Jul 2002 18:32:47 -0000	1.4
  @@ -1,3 +1,4 @@
  +<?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
   
   <document>
  @@ -5,6 +6,7 @@
       <title>Excalibur Configuration - Overview</title>
       <authors>
         <person name="Stephen McConnell" email="mcconnell@apache.org"/>
  +      <person name="Peter Royal" email="proyal@apache.org"/>
       </authors>
     </header>
     <body>
  @@ -21,17 +23,31 @@
   between two configuration instances.  This is helpful when you have a default
   configuration together with a configuration that contains overriding values.
   The level of cascading of configurations is arbitary.  The CascadingConfiguration
  -implementation impements the classic Configuration interface and delegates 
  -invocations to the base configuration.  If the delegate operation fails, the 
  -implementation will attempt to resolve the invocation against the parent 
  +implementation impements the classic Configuration interface and delegates
  +invocations to the base configuration.  If the delegate operation fails, the
  +implementation will attempt to resolve the invocation against the parent
   configuration.  Both base and parent configuration reference can be classic or
   cascading enabling the creation of complex configuration graphs.
           </p>
         </s2>
  -      <s2 title="CascadingConfiguration">
  +      <s2 title="ConfigurationUtil">
           <p>
  -Provides a static list operation that is helpful in debugging.  The list 
  +Provides a static list operation that is helpful in debugging.  The list
   operation generates a simple string representation of a configuration.
  +        </p>
  +        <p>
  +Also provides a branch operation to take a Configuration object and rename it but
  +retain all attributes and children
  +        </p>
  +      </s2>
  +      <s2 title="ConfigurationMerger">
  +        <p>
  +Similar to the CascadingConfiguration in that it takes two Configuration's and
  +makes one. The ConfigurationMerger can take a "layer" and a "base" and merge
  +the layer with the base. The ConfigurationMerger goes a step farther than the
  +CascadingConfiguration in that it provides a consistent view of
  +Configuration.getChildren() based off of meta-attributes that can exist in the
  +layer.
           </p>
         </s2>
       </s1>
  
  
  
  1.2       +1 -0      jakarta-avalon-excalibur/configuration/src/xdocs/menu.xml
  
  Index: menu.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/configuration/src/xdocs/menu.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- menu.xml	19 Jul 2002 16:24:40 -0000	1.1
  +++ menu.xml	19 Jul 2002 18:32:47 -0000	1.2
  @@ -3,6 +3,7 @@
   
     <menu name="About">
       <item href="index.html" name="Overview"/>
  +    <item href="configuration-merger.html" name="Configuration Merger"/>
       <item href="http://jakarta.apache.org/avalon/excalibur/index.html" name="Excalibur Home"/>
       <item href="http://jakarta.apache.org/builds/jakarta-avalon-excalibur/release" name="Download"/>
       <item href="api" name="API Docs"/>
  
  
  
  1.4       +16 -4     jakarta-avalon-excalibur/configuration/README.txt
  
  Index: README.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/configuration/README.txt,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- README.txt	13 Jul 2002 18:24:29 -0000	1.3
  +++ README.txt	19 Jul 2002 18:32:47 -0000	1.4
  @@ -13,16 +13,28 @@
   between two configuration instances.  This is helpful when you have a default
   configuration together with a configuration that contains overriding values.
   The level of cascading of configurations is arbitary.  The CascadingConfiguration
  -implementation impements the classic Configuration interface and delegates 
  -invocations to the base configuration.  If the delegate operation fails, the 
  -implementation will attempt to resolve the invocation against the parent 
  +implementation impements the classic Configuration interface and delegates
  +invocations to the base configuration.  If the delegate operation fails, the
  +implementation will attempt to resolve the invocation against the parent
   configuration.  Both base and parent configuration reference can be classic or
   cascading enabling the creation of complex configuration graphs.
   
   ConfigurationUtil
   -----------------
  -Provides a static list operation that is helpful in debugging.  The list 
  +Provides a static list operation that is helpful in debugging.  The list
   operation generates a simple string representation of a configuration.
  +
  +Also provides a branch operation to take a Configuration object and rename it but
  +retain all attributes and children
  +
  +ConfigurationMerger
  +-------------------
  +Similar to the CascadingConfiguration in that it takes two Configuration's and
  +makes one. The ConfigurationMerger can take a "layer" and a "base" and merge
  +the layer with the base. The ConfigurationMerger goes a step farther than the
  +CascadingConfiguration in that it provides a consistent view of
  +Configuration.getChildren() based off of meta-attributes that can exist in the
  +layer.
   
   
   
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>