anchor.diff:  registration file in each JAR containing configurations. This registration file will be located at
   +jar:/META-INF/org.ocpsoft.rewrite.config.ConfigurationProvider+. 
   
  -NOTE: Alternate methods of configuration are available, such as link:../annotations/[Rewrite Annotations],
  +NOTE: Alternate methods of configuration are available, such as link:./annotations/[Rewrite Annotations],
   link:../prettyfaces/[PrettyFaces XML and Annotations], and via link:../../integration/cdi[cdi] and 
   link:../../integration/spring[spring]; these methods may be used to avoid the need for a provider registration file.
   
   === 4. Verify that your configuration is installed
   
  -Before link:../[configuring Rewrite], you may wish to verify that your provider has
  +Before link:./[configuring Rewrite], you may wish to verify that your provider has
   been properly installed and activated. To do this, start your application and look at the server output, where
   you should see a summary of each active Rewrite extension, and all of your registered configuration providers:
   
  
positive.code: 
  As can be seen above, configuring Rewrite may be performed using the +ConfigurationBuilder+ class, which allows
  addition of pre-constructed +Rule+ instances, as well as definition of custom rules using +Condition+, +Operation+, 
  and other link:../[configuration objects]. Your configuration can be as simple or complex as you wish:
  
  [source,java]
  .Example Configuration
  
negative.code: 
  Rewrite is a highly extendable framework, and there are many pre-defined configuration options available to help achieve specialized and specific results; however, if no pre-defined configuration object exists, it is easy to create one that fills the gaps.
   
  Read the link:./[configuration manual] for more information on creating custom rules and rule primitives.
  