anchor.diff:  `java.util.Properties` that contains the properties which should be
   preferred to be used.
   
  -include::../../../components/camel-test-blueprint/src/test/java/org/apache/camel/test/blueprint/ConfigAdminOverridePropertiesTest.java[]
  +[source,java]
  +----
  +@Override
  +protected Properties useOverridePropertiesWithPropertiesComponent() {
  +    Properties extra = new Properties();
  +    extra.put("destination", "mock:extra");
  +    extra.put("greeting", "Bye");
  +    return extra;
  +}
  +----
   
   This can be done from any of the Camel Test kits, such as `camel-test`,
   `camel-test-spring` and `camel-test-blueprint`.
  
positive.code: You can do both as well. Here is a complete example. First we have the
  Blueprint XML file:
  
  include::../../../components/camel-test-blueprint/src/test/resources/org/apache/camel/test/blueprint/configadmin-loadfileoverride.xml[]
  
  And in the unit test class we do as follows:
  
  include::../../../components/camel-test-blueprint/src/test/java/org/apache/camel/test/blueprint/ConfigAdminLoadConfigurationFileAndOverrideTest.java[]
  
  And the `etc/stuff.cfg` configuration file contains:
  
  
negative.code: Now if you want to override these Blueprint properties from an unit
  test, you can do this as shown below:
  
  [source,java]
  ----
  protected String useOverridePropertiesWithConfigAdmin(Dictionary props) {
      // add the properties we want to override
      props.put("greeting", "Bye");
  
      // return the PID of the config-admin we are using in the blueprint xml file
      return "my-placeholders";
  }
  ----
  
  To do this we override and implement the
  `useOverridePropertiesWithConfigAdmin` method. We can then put the
  