XML DOM Parser Errors

When Firefox encounter a parser error, it loads an XML document containing the error

Parser Error in Firefox

When trying to open an XML document, a parser-error may occur.

Unlike Internet Explorer, if Firefox encounters an error, it loads an XML document containing the error description.

The root node name of the XML error document is "parsererror". This is used to check if there is an error.

XML Error

In the following code we let the parser load an XML document that is not well-formed.

(You can read more about well-formed and valid XML in our XML tutorial)

xmlDoc=document.implementation.createDocument("","",null);
xmlDoc.async=false;
xmlDoc.load("note_error.xml");

if (xmlDoc.documentElement.nodeName=="parsererror")
{
errStr=xmlDoc.documentElement.childNodes[0].nodeValue;
errStr=errStr.replace(/</g, "&lt;");
document.write(errStr);
}
else
{
document.write("XML is valid");
}

Example explained:

1. Load the xml file
2. Check if the nodeName of the root node is "parsererror"
3. Load the error string into a variable "errStr"
4. Replace "<" characters with "&lt;" before the error string can be written as HTML

Try it yourself or just look at the XML file

Note: Only Internet Explorer will actually check your XML against the DTD. Firefox will not.

Cross Browser Error Check

Here we have created an XML load function that checks for parser errors in both Internet Explorer and Firefox:

function loadXMLDocErr(dname) 
{
try //Internet Explorer
  {
  xmlDoc=new ActiveXObject("Microsoft.XMLDOM");
  xmlDoc.async=false;
  xmlDoc.load(dname); 

  if (xmlDoc.parseError.errorCode != 0) 
    {
    alert("Error in line " + xmlDoc.parseError.line + 
    " position " + xmlDoc.parseError.linePos + 
    "\nError Code: " + xmlDoc.parseError.errorCode + 
    "\nError Reason: " + xmlDoc.parseError.reason + 
    "Error Line: " + xmlDoc.parseError.srcText);
    return(null);
    }
  }
catch(e)
  {
  try //Firefox
    {
    xmlDoc=document.implementation.createDocument("","",null);
    xmlDoc.async=false;
    xmlDoc.load(dname);
    if (xmlDoc.documentElement.nodeName=="parsererror")
      {
      alert(xmlDoc.documentElement.childNodes[0].nodeValue);
      return(null);
      }
    }
  catch(e) {alert(e.message)}
  }
try 
  {
  return(xmlDoc);
  }
catch(e) {alert(e.message)}
return(null);
}

Example explained - Internet Explorer:

1. The first line creates an empty Microsoft XML document object
2. The second line turns off asynchronized loading, to make sure that the parser will not continue execution of the script before the document is fully loaded
3. The third line tells the parser to load an XML document called "note_error.xml"
4. If the errorCode property of the parseError object is different from "0", alert the error and exit the function
5. If the errorCode property is "0", return the XML document

Example explained - Firefox:

1. The first line creates an empty XML document object.
2. The second line turns off asynchronized loading, to make sure that the parser will not continue execution of the script before the document is fully loaded.
3. The third line tells the parser to load an XML document called "note_error.xml".
4. If the returned document is an error document, alert the error and exit the function
5. If not, return the XML document

Try it yourself or just look at the XML file

Altova® XMLSpy® - The world's best-selling XML editor!

Whether you're new to XML or already an advanced user, the user-friendly views and powerful entry helpers, wizards, and debuggers in XMLSpy are designed to meet your XML and Web services development needs from start to finish.

• XML editor
• Graphical XML Schema / DTD editors
• XSLT 1.0/2.0 editor, debugger, profiler
• XQuery editor, debugger, profiler
• Support for Office Open XML (OOXML)
• Graphical WSDL editor & SOAP debugger
• Java, C#, C++ code generation
• And much more!

Download a fully functional free 30-day trial today!

Jump to: Top of Page or HOME or Printer friendly page

W3Schools provides material for training only. We do not warrant the correctness of its contents. The risk from using it lies entirely with the user. While using this site, you agree to have read and accepted our terms of use and privacy policy.

Copyright 1999-2009 by Refsnes Data. All Rights Reserved.

W3Schools was converted to XHTML in December 1999