====== Troubleshooting issues during the creation of mapping objects ====== 

Below you'll find methods for basic troubleshooting for issues encountered during the creation of mapping objects in eBiss, which cannot be resolved automatically.

===== Typical problems when using a XSD ===== 

Listed below are typical causes for errors when a XSD is used to create a mapping object.

==== External schema location in import ====

External schema locations can lead to errors during the creation, especially if the internet connection to the referenced schema is not up to par.

e.g.:
  <xs:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd" />
  
In such cases, it can become necessary to download the XSD and change the "schemaLocation" to reference the local copy of the XSD.

  <xs:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="xmldsig-core-schema.xsd" />

==== Issues caused by referenced element definitions ====

The use of a referenced element definition can, in some rare cases, lead to errors during the creation of the mapping object:

  <xs:element ref="ns:ActualElementDef" /> 
  
In such cases, the following error message will be displayed, specifying the element, which causes the problem: \\  
"Could not create the XmlDocument in XsdMapObjectGenerator.ReadMessage.The 'http://...ns:ActualElementDef' element is not declared."

These issues can only be resolved by use of [[en:programmierung:typbibliotheken:typeditor|]] at the moment. This is done by commenting out or removing the element, creating the rest of the structure and then adding in the missing element using the correct type.