title: What is the practical difference between Xerces2-J StandardParserConfiguration and IntegratedParserConfiguration?
body: <p>According to Xerces2-J <a href="https://xerces.apache.org/xerces2-j/faq-xni.html#faq-3" rel="nofollow noreferrer">XNI FAQ</a>, the IntegratedParserConfiguration</p>
  <blockquote>
  <p>Extends StandardParserConfiguration by including a scanner that integrates both scanning of the document and binding namespaces.</p>
  </blockquote>
  <p>In my testing, using a SAX parser configured with either StandardParserConfiguration or IntegratedParserConfiguration behaved the same, in that they both were able to parse XML documents using namespaces and report the namespace URI in callback handlers.</p>
  <p>That is, overriding the <a href="http://www.saxproject.org/apidoc/org/xml/sax/helpers/DefaultHandler.html" rel="nofollow noreferrer">DefaultHandler</a> as follows reported the same information when parsing the same documents containing elements belonging to some namespace:</p>
  <pre><code>    @Override
      public void startElement(String uri, String name, String qName, Attributes atts) {
          if (&quot;&quot;.equals (uri)) {
              System.out.println(&quot;Start element: &quot; + qName);
          } else {
              System.out.println(&quot;Start element: {&quot; + uri + &quot;}&quot; + name);
          }
      }
  
      @Override
      public void endElement (String uri, String name, String qName) {
          if (&quot;&quot;.equals (uri)) {
              System.out.println(&quot;End element: &quot; + qName);
          } else {
              System.out.println(&quot;End element:   {&quot; + uri + &quot;}&quot; + name);
          }
      }
  </code></pre>
  <p>What is the practical difference between the StandardParserConfiguration and IntegratedParserConfiguration?</p>