commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject cvs commit: jakarta-commons/digester/src/java/org/apache/commons/digester/plugins package.html
Date Tue, 17 Aug 2004 20:17:44 GMT
rdonkin     2004/08/17 13:17:44

  Modified:    digester/src/java/org/apache/commons/digester/plugins Tag:
                        RELEASE_DIGESTER_1_6_0_BRANCH package.html
  Log:
  Fixed a few tpyos
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.5.2.1   +7 -7      jakarta-commons/digester/src/java/org/apache/commons/digester/plugins/package.html
  
  Index: package.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/digester/src/java/org/apache/commons/digester/plugins/package.html,v
  retrieving revision 1.5
  retrieving revision 1.5.2.1
  diff -u -r1.5 -r1.5.2.1
  --- package.html	18 Apr 2004 07:28:36 -0000	1.5
  +++ package.html	17 Aug 2004 20:17:44 -0000	1.5.2.1
  @@ -78,7 +78,7 @@
   pattern)</code> on the class being "plugged in", or</li>
   <li> providing a separate "rule info" class, somewhat in the spirit of 
   "BeanInfo" classes for java beans, or</li>
  -<li> providing an xmlrules file which defines the associated parsing rules./li>
  +<li> providing an xmlrules file which defines the associated parsing rules.</li>
   </ul>
   If a plugin class has a no-parameter constructor, does not expect any subtags, 
   and is satisfied with mapping any attributes on the parent xml tag to 
  @@ -92,8 +92,8 @@
   <h2> Plugin Declarations </h2>
   
   As well as the syntax shown above, where plugin classnames were defined
  -as they were used, plugin classes can be pre-dedeclared (provided the application
  -associates a PluginDeclarationRule with a tag for that purpose). Example:
  +as they were used, plugin classes can be pre-declared (provided the application
  +associates a <code>PluginDeclarationRule</code> with a tag for that purpose).
Example:
   <p>
   The plugin class can be declared once:
   <pre>
  @@ -104,12 +104,12 @@
     &lt;sometag plugin-id="widget" ... &gt;
   </pre>
   
  -<h2> Possible Applications </h2>
  +<h2> Suggested Applications </h2>
   
   Any application where user-specific operations may need to be performed
   that cannot be known in advance by the initial application developer may
  -benefit from this module. Applications in the style of the apache projects 
  -listed at the top of this page (log4j, cocoon, ant) are examples.
  +benefit from this module. Applications in the style of the Apache projects 
  +listed at the top of this page (Log4j, Cocoon, Ant) are examples.
   <p>
   Note also that plugged-in classes can themselves allow user-defined classes
   to be plugged in within their configuration. This allows a very simple
  @@ -130,7 +130,7 @@
   <code>&lt;statement plugin-id="if"&gt;</code> cannot become &lt;if&gt;.
   <p>
   An instance of "PluginRules" must be used as the Rules implementation
  -for the digester (see example). However a PluginRules can use any other Rules
  +for the Digester (see example). However a PluginRules can use any other Rules
   implementation as its rule-matching engine, so this is not a significant issue.
   Plugged-in classes may only use the default RulesBase matching for the rules
   they add dynamically.
  
  
  

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


Mime
View raw message