gotten grip on the
automatic feature of log4j, I started liking it. But it seems servlets
is the way to go at this time.
However my servlet isn't such a fancy one like yours, so I would be
interested in the source!
Tom
Charles Hudak wrote:
Looks the attachment got filtered out. If anyone
I created one of these for our application.
It also handles clustered servers so if you have multiple servers using the
same config, it will do a reload on all of them by hitting the main url
(useful if you are behind a firewall or using a big ip box, like we are).
You can also have specific
Looks the attachment got filtered out. If anyone is interested, they can
email me for the source. Sorry, but I don't have access to the cvs
repository behind our firewall to upload it.
-Original Message-
From: Charles Hudak [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 15:57
Doubtful since J++ is stuck at something like JDK 1.1.7 which didn't include
the Collections libraries, among other things, that JDK 1.2 added.
-Original Message-
From: Chang, Betty [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2003 15:39
To: [EMAIL PROTECTED]
Subject: Can log4j
Support Ceki and buy the manual.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2003 13:37
To: [EMAIL PROTECTED]
Subject: filter some class to one file, different class to another file
Hello,
I'm new to configuring my log4j.xml file,
Most of the examples show the 'programmatic' use of Log4j. In most real
applications, the logging is integrated into the code and the controlled
externally via the configuration.
In any event, this is how I typically use loggers in my classes:
package com.mystuff;
public class MyClass
{
Actually, if you look at the code, the connection is closed in the finalize
method, not after every call to the execute method so the connection will
only be closed when the object is GC'd. The code is actually fairly fragile
in that if the connection times out (and is summarilly closed), the
log4j is fail stop. Logging doesn't and shouldn't throw an exception to your
application and cause it to crash.
-Original Message-
From: Raveendranath, Rohith (LNG - AUS)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 17:12
To: 'Log4J Users List'
Subject: Behaviour in Log4j
-Original Message-
From: Charles Hudak [mailto:[EMAIL PROTECTED]
Sent: Friday, 29 August 2003 10:23 AM
To: 'Log4J Users List'
Subject: RE: Behaviour in Log4j when Logfile is deleted.
log4j is fail stop. Logging doesn't and shouldn't throw an exception to your
application and cause
There are obviously many ways to do this.
The way I do it is I created a LogInitializer servlet that is loaded on
startup and uses a single configuration file. Since I'm really only
concerned about the logging from MY code and not any of the open
source/other components that I have installed,
make it myself)? All you
really need to do is a File.createDirs() in FileAppender.setFile(...).
Charles Hudak
Software Engineering Manager
Arrowhead General Insurance/YouZoom, Inc.
[EMAIL PROTECTED]
858.320.6800x6344
rant
I agree with Kevin. Java used to have a 'private-protected' access modifier
that was synonymous with C++ protected but they dropped it after 1.0. This
was a bad idea, IMHO. Often you'd like to restrict access to variables to
the class and its subclasses only. Protected doesn't give you this
Sounds like you are going to have to setup your appenders dynamically in
each class or delegate the appender construction to an 'AppenderFactory'.
The Factory will take a package name as a parameter. It will construct an
appender for each package and then cache the package name. Additional calls
13 matches
Mail list logo
