logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject cvs commit: jakarta-log4j-sandbox/src/java/org/apache/log4j/jdbc JDBCReceiver.java
Date Mon, 15 Dec 2003 17:00:55 GMT
ceki        2003/12/15 09:00:55

  Modified:    src/java/org/apache/log4j/jdbc JDBCReceiver.java
  Log:
  
  small doco update
  
  Revision  Changes    Path
  1.12      +3 -3      jakarta-log4j-sandbox/src/java/org/apache/log4j/jdbc/JDBCReceiver.java
  
  Index: JDBCReceiver.java
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j-sandbox/src/java/org/apache/log4j/jdbc/JDBCReceiver.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- JDBCReceiver.java	2 Dec 2003 23:28:31 -0000	1.11
  +++ JDBCReceiver.java	15 Dec 2003 17:00:55 -0000	1.12
  @@ -89,7 +89,7 @@
    * param name="sql" value='select logger as LOGGER, timestamp as TIMESTAMP, 
    * level as LEVEL, thread as THREAD, message as MESSAGE, ndc as NDC, mdc as MDC, 
    * class as CLASS, method as METHOD, file as FILE, line as LINE, 
  - * concat("{{log4japp,databaselogs,log4jmachinename,mymachine,log4jid,", COUNTER, "}}")

  + * concat("{{application,databaselogs,hostname,mymachine,log4jid,", COUNTER, "}}") 
    * as PROPERTIES, "" as EXCEPTION from logtable' 
    *
    * In other words, if a number of LoggingEvent properties were combined into one field
  @@ -102,7 +102,7 @@
    * exceptions, but the fields can be defined in the SQL statement and included in
    * the event.
    *
  - * This means that log4japp and/or log4jmachinename properties can be provided and
  + * This means that application and/or hostname properties can be provided and
    * the properties may be used to create a unique tab for the events.
    *
    * Both {{name, value, name2, value2}} formats and formats without the double braces
  @@ -121,7 +121,7 @@
    * 
    * Include the properties as provided in the example SQL above to successfully get 
    * events to be delivered into Chainsaw.  The log4jid property must be provided by the

  - * database and the timestamp field must be a datetime.  The log4jmachinename and log4japp

  + * database and the timestamp field must be a datetime.  The hostname and application 
    * properties are specific to your application and define which unique tab the events are

    * delivered to.
    * 
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org


Mime
View raw message