RE: getClassName from locationInfo object

2002-06-12 Thread Steve . Lewis
e quickest way to handle the problem - extend JDBCAppender yourself and just over-ride getLogStatement() -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 8:15 AM To: Log4J Users List Subject: RE: getClassName from locationInfo object

RE: getClassName from locationInfo object

2002-06-12 Thread Klein, Scott @ TW
seeing as it may be the quickest way to handle the problem - extend JDBCAppender yourself and just over-ride getLogStatement() -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 8:15 AM To: Log4J Users List Subject: RE: getClassName from

RE: getClassName from locationInfo object

2002-06-12 Thread Steve . Lewis
TW" cc: 06/12/2002 10:37 Subject: RE: getClassName from locationInfo object

RE: getClassName from locationInfo object

2002-06-12 Thread Klein, Scott @ TW
]] Sent: Wednesday, June 12, 2002 5:19 AM To: Log4J Users List Subject: RE: getClassName from locationInfo object Well, I'm extending the JDBCAppender to use its own thread, and to use a prepared statement, so I have my own columns for classname, etc. I'm using (in development) Wi

RE: getClassName from locationInfo object

2002-06-12 Thread Steve . Lewis
"RUTHERFURD, Michael" To: Log4J Users List <[EMAIL PROTECTED]> Subject: RE: getClas

RE: getClassName from locationInfo object

2002-06-11 Thread RUTHERFURD, Michael
The ? probably means that LocationInfo couldn't parse the Throwable's stack trace that is used to determine class name, method name, line number etc. What OS are you using, as I had this problem in Websphere on AS400? I ended up having to write a kludged version of LocationInfo to parse the weird