title: Wrap log4j or create custom logger?
body: <p>I have an application that needs to log two different types of messages: application log messages and audit messages. Application log messages match the standard lo4j <code>Logger</code> perfectly, but there are several required parameters for the audit log.</p>
  
  <p>I think I need to wrap log4j to add the additional required parameters to the <code>debug()</code>, <code>info()</code>, etc methods, but I hate the idea of wrapping log4j. Should I:</p>
  
  <ol>
  <li>Wrap log4j completely and provide my own <code>Logger</code> class that calls a log4j logger behind the scenese?</li>
  <li>Extend the log4j <code>Logger</code> class and add "audit log" methods with my required parameters?</li>
  <li>Do something even more elegant so I'm not wrapping a logging library...</li>
  </ol>