anchor.diff:    required client configuration (for client1). Refer to the scopes section for more details.
   
   
  -=== Using the Configuration Servlet
  -
  -Additionally to the fully built-in solution, it is also possible to integrate the server module with a standard
  +=== Using the Configuration Servlets
  +
  +Additionally to the fully built-in solution, it is also possible to integrate the Tamaya server module with a standard
   Java EE servlet container. Tamaya provides 2 servlet implementations:
   
   * the servlet +org.apache.tamaya.server.FilteredConfigServlet+ can be used to register access to configurations
  
positive.code: -----------------------------------------------
  
  
  .Formatting for application/html
  
  [source, html]
  -----------------------------------------------
  
negative.code: my.full.packagename.ClientScopeProvider
  -----------------------------------------------
  
  ==== Adapting the Way Configuration is Derived
  
  Finally the effective readong and configuration handling logic can also be replaced or improved. This can be
  done by registering your own implementation of the interface +ConfigProviderService+:
  
  [source, java]
  ------------------------------------------------
  