How to parse invalid XML in Java

Question

Currently, I'm working on a feature that involves parsing XML that we receive from another product. I decided to run some tests against some actual customer data, and it looks like the other product is allowing input from users that should be considered invalid. Anyways, I still have to try and figure out a way to parse it. We're using javax.xml.parsers.DocumentBuilder and I'm getting an error on input that looks like the following.

<xml>
  ...
  <description>Example:Description:<THIS-IS-PART-OF-DESCRIPTION></description>
  ...
</xml>

As you can tell, the description has what appears to be an invalid tag inside of it (<THIS-IS-PART-OF-DESCRIPTION>). Now, this description tag is known to be a leaf tag and shouldn't have any nested tags inside of it. Regardless, this is still an issue and yields an exception on DocumentBuilder.parse(...)

I know this is invalid XML, but it's predictably invalid. Any ideas on a way to parse such input?

Answer 1

That "XML" is worse than invalid – it's not well-formed.

An informal assessment of the predictability of the transgressions does not help. That textual data is not XML. No conformant XML tools or libraries can help you process it.

Options, most desirable first:

1. Have the provider fix the problem on their end. Demand well-formed XML. (Technically the phrase well-formed XML is redundant but may be useful for emphasis.)

2. Use a tolerant markup parser to cleanup the problem ahead of parsing as XML:

   • Standalone: xmlstarlet has robust recovering and repair capabilities 

     xmlstarlet fo -o -R -H -D bad.xml 2>/dev/null

   • Standalone and C: HTML Tidy works with XML too.

   • Python: Beautiful Soup is Python-based.
   • Java: JSoup focuses on HTML. FilterInputStream can be used for preprocessing cleanup.

   • .NET:

     • XmlReaderSettings.CheckCharacters can be disabled to get past illegal XML character problems.

     • @jdweng reports that XmlReader.ReadToFollowing() can sometimes be used to work-around XML syntactical issues, but note rule-breaking warning in #3 below.

     • Microsoft.Language.Xml.XMLParser is said to be “error-tolerant”.
   • PHP: See DOMDocument::$recover and libxml_use_internal_errors(true).
   • Ruby: Nokogiri supports “Gentle Well-Formedness”.
   • R: See htmlTreeParse() for fault-tolerant markup parsing in R.

3. Process the data as text manually using a text editor or programmatically using character/string functions. Doing this programmatically can range from tricky to impossible as what appears to be predictable often is not -- rule breaking is rarely bound by rules.

   • For invalid character errors, use regex to remove/replace invalid characters:
     • PHP: preg_replace('/[^\x{0009}\x{000a}\x{000d}\x{0020}-\x{D7FF}\x{E000}-\x{FFFD}]+/u', ' ', $s);
     • Ruby: string.tr("^\u{0009}\u{000a}\u{000d}\u{0020}-\u{D7FF}\u{E000‌​}-\u{FFFD}", ' ')
     • JavaScript: inputStr.replace(/[^\x09\x0A\x0D\x20-\xFF\x85\xA0-\uD7FF\uE000-\uFDCF\uFDE0-\uFFFD]/gm, '')

   • For ampersands, use regex to replace matches with &amp;:

     &(?!(?:#\d+|#x[0-9a-f]+|\w+);)

   Note that the above regular expressions won't take comments or CDATA sections into account.