anchor.diff:       location="classpath:citrus/samples/sayGoodbye.xsd"/>
   ----
   
  -The listing above defines two root qname mappings - one for *HelloRequest* and one for *GoodbyeRequest* message types. An incoming message of type <HelloRequest> is then mapped to the respective schema and so on. With this dedicated mappings you are able to control which schema is used on a XML request, regardless of target namespace definitions.
  +The listing above defines two root qname mappings - one for *HelloRequest* and one for *GoodbyeRequest* message types.
  +An incoming message of type <HelloRequest> is then mapped to the respective schema and so on. With this dedicated
  +mappings you are able to control which schema is used on a XML request, regardless of target namespace definitions.
   
   [[schema-mapping-strategy-chain]]
   ==== Schema mapping strategy chain
   
  -Let's discuss the possibility to combine several schema mapping strategies in a logical chain. You can define more than one mapping strategy that are evaluated in sequence. The first strategy to find a proper schema definition file in the repository wins.
  +Let's discuss the possibility to combine several schema mapping strategies in a logical chain. You can define more than
  +one mapping strategy that are evaluated in sequence. The first strategy to find a proper schema definition file in the
  +repository wins.
   
   [source,xml]
   ----
  
positive.code: </receive>
  ----
  
  This mandatory schema validation might sound annoying to you but in our opinion it is very important to validate the structure of the received XML messages, so disabling the schema validation should not be the standard for all tests. Disabling automatic schema validation should only apply to very special situations. So please try to put all available schema definitions to the schema repository and you will be fine.
  
  [[wsdl-schemas]]
  ==== WSDL schemas
  
  In SOAP WebServices world the WSDL (WebService Schema Definition Language) defines the structure an nature of the XML messages exchanged across the interface. Often the WSDL files do hold the XML schema definitions as nested elements. In Citrus you can directly set the WSDL file as location of a schema definition like this:
  
  [source,xml]
  ----
  
negative.code: </bean>
  ----
  
  So the schema mapping chain uses both *RootQNameSchemaMappingStrategy* and *TargetNamespaceSchemaMappingStrategy* in
  combination. In case the first root qname strategy fails to find a proper mapping the next target namespace strategy
  comes in and tries to find a proper schema.
  
  [[schema-definition-overruling]]
  ==== Schema definition overruling
  
  Now it is time to talk about schema definition settings on test action level. We have learned before that Citrus
  tries to automatically find a matching schema definition in some schema repository. There comes a time where you as a
  tester just have to pick the right schema definition by yourself. You can overrule all schema mapping strategies in
  Citrus by directly setting the desired schema in your receiving message action.
  
  [source,xml]
  ----
  