This package adds Log4J functionality to Jetty Server logging.  Currently, only HTTP Request 
Logging has been implemented.  

Once unzipped, this package should be placed in the {server-home}/contrib directory.
Running mvn (install is default) on this contrib module will install all necessary libraries 
and config files.  Running mvn clean will remove them.  

Once installed, this package may be used by adding {server-home}/lib/logging-log4j/*.jar to the 
Jetty server's classpath.  The config file etc/jetty-logging-log4j.xml must also be passed to 
the start.jar as a parameter before etc/jetty.xml.

NOTE: {server-home}/lib/log4j/*.jar must NOT be added to the server's classpath.
This could (and probably would) cause log4j configuration errors and log4j library
version collisions.

Log4J HTTP Requset Loggers can be added to the Jetty server or to contexts as shown in the 
examples that follow.  Appenders are configured in etc/log4j-jetty-config.xml.  


    <!-- define server-wide loggers in jetty.xml -->

    <!-- =========================================================== -->
    <!-- Configure Request Log                                       -->
    <!-- Request logs  may be configured for the entire server here, -->
    <!-- or they can be configured for a specific web app in a       -->
    <!-- contexts configuration (see $(jetty.home)/contexts/test.xml -->
    <!-- for an example).                                            -->
    <!-- =========================================================== -->
    <Ref id="RequestLog">
      <Set name="requestLog">

        <!-- original NCSARequestLog for server wide access request logging
        <New id="RequestLogImpl" class="org.mortbay.jetty.NCSARequestLog">
          <Set name="filename"><SystemProperty name="jetty.logs" default="./logs"/>/yyyy_mm_dd.request.log</Set>
          <Set name="filenameDateFormat">yyyy_MM_dd</Set>
          <Set name="retainDays">90</Set>
          <Set name="append">true</Set>
          <Set name="extended">true</Set>
          <Set name="logCookies">false</Set>
          <Set name="LogTimeZone">GMT</Set>
        </New> -->

        <!-- Log4J Server Wide Logger should always be created.  If it is not to be -->
        <!-- used, it should be defined with no appenders in the log4j config. -->
        <!-- The same config options are available for this Request Logger as were -->
        <!-- available for the NCSARequestLog, minus the file name and rotation options, -->
        <!-- which would be configured in log4j-jetty-config.xml -->
        <New id="RequestLogImpl" class="org.mortbay.jetty.Log4JRequestLogWrapper">
            <!-- The implementing class name is added to the logger name, giving a final Logger name of -->
            <!-- org.mortbay.jetty.Log4JRequestLogImpl.ServerWide -->
            <Set name="accessLoggerName">ServerWide</Set>
            <Set name="extended">true</Set>
            <Set name="logCookies">false</Set>
            <Set name="LogTimeZone">GMT</Set>
        </New>

      </Set>
    </Ref>



  <!-- define context-specific loggers in contexts/{context}.xml -->

  <!-- Individual context Request Logger added here.  -->
  <Call name="addHandler">
    <Arg>
    <New class="org.mortbay.jetty.handler.RequestLogHandler">
      <Set name="RequestLog">
        <New id="RequestLogImpl" class="org.mortbay.jetty.Log4JRequestLogWrapper">
          <!-- The implementing class name is added to the logger name, giving a final Logger name of -->
          <!-- org.mortbay.jetty.Log4JRequestLogImpl.Test -->
          <Set name="accessLoggerName">Test</Set>
          <!-- Default logging options used in this case. -->
        </New>
      </Set>
    </New>
    </Arg>
  </Call>