Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>It seems like you are parsing your response with a namespace aware XML parser but the namespace support of the parser isn't turned on. This results in a clash of two rules.</p> <ol> <li>When parsing an XML document with namespaces, all elements and attributes are referred to with their expanded name. Expanded name consist of the namespace URI and the local name of the element/attribute. If the parser is not namespace aware, the URI part of the name is lost. Therefore some parsers with namespace support also drop the namespace prefix if the namespace support is not turned on.</li> <li>An element is not allowed to contain two attributes with same (expanded) name. In such cases other one of the attributes is lost. Normally a namespace aware XML parser would see those two <code>type</code> attributes as <code>{http://www.w3.org/2001/XMLSchema-instance}type</code> and <code>type</code> (using James Clark notation). A non-namespace aware parser should return attribute names <code>xsi:type</code> and <code>type</code>. In these cases there is no name collision and everything should work ok.</li> </ol> <p>Problems arise if your parser knows that a colon <code>:</code> works as a namespace prefix delimiter but the parser is not using namespaces and therefore drops the delimiter and the namespace prefix. Then both of these attributes will get name <code>type</code> and other one of these is lost/overwritten because of the attribute name uniqueness rule.</p> <p>Solution: Set namespace support on for your parser or switch to another more capable parser. Hopefully someone can give more specific answers if you update your question with information on how the XML file is being parsed.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload