anchor.diff:  [[root-qname-mapping-strategy]]
   ==== Root QName Mapping Strategy
   
  -The next possibility for mapping incoming request messages to a schema definition is via the XML root element QName. Each XML message payload starts with a root element that usually declares the type of a XML message. According to this root element you can set up mappings in the schema repository.
  +The next possibility for mapping incoming request messages to a schema definition is via the XML root element QName.
  +Each XML message payload starts with a root element that usually declares the type of a XML message. According to this
  +root element you can set up mappings in the schema repository.
   
   [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:     class="com.consol.citrus.xml.schema.TargetNamespaceSchemaMappingStrategy"/>
  ----
  
  The *sayHello.xsd* schema file defines a target namespace
  (http://consol.de/schemas/sayHello.xsd)[http://consol.de/schemas/sayHello.xsd)]:
  
  [source,xml]
  ----
  