title: Using DOMConfigurator.configureAndWatch in case of migrating from Log4j 1.x to 2.x using Log4j 1.x bridge
body: <p>According to &quot;Migrating from Log4j 1.x to 2.x&quot; using Log4j 1.x bridge documentation:</p>
  <blockquote>
  <p>Applications can migrate by just using the bridge without further code
  changes, if they meet the following requirements: They must not
  configure by calling the Log4j 1.x classes DOMConfigurator</p>
  </blockquote>
  <p>My application uses DOMConfigurator.configureAndWatch().<br />
  I just removed log4j1 jars from my application and added log4j2+Log4j 1.x bridge jars.<br />
  And I do not see any issues with logging.<br />
  Can someone explain what could be wrong with this approach?</p>