Hi all
I have a server application which can serve multiple clients. The logging
occurs in files separated by client. (BTW: This is accomplished by supplying a
own RepositorySelector which uses certain values in MDC).
Therefore the file name within the configurtion file
I agree with Paul because it would make it a lot easier to see if I want
to use the dbappender and have all the classes in one jar, rather than
figure out what settings i need.
John
[EMAIL PROTECTED] 4/6/2005 8:09:47 PM
At 10:37 AM 4/7/2005 +1000, you wrote:
The build system now builds core,
Heri,
I assume the overriding of the filename happens after the client does the
standard log4j configuration, so log.log is created anyway before you
programmatically intervene. You could also programmatically delete log.log.
Suggestion: a (cleaner?) alternative for 'overriding the filename' is
At 03:09 AM 4/7/2005, Jacob Kjome wrote:
At 10:37 AM 4/7/2005 +1000, you wrote:
The build system now builds core, and optional jars. If you don't setup
your build.properties correctly, the build system will detect it does
not have enough of the dependencies to build the other optional jars,
which
Well, here is what I am trying to do. I am trying to test the
dbAppender functionality to see if this is something that we want to use
since we think this would be very helpful and also that the JDBCAppender
is now obsolete. I feel that a log4j-all file would be helpful because
in the end, that
At 02:42 PM 4/7/2005, Bender Heri wrote:
Hi all
I have a server application which can serve multiple clients. The logging
occurs in files separated by client. (BTW: This is accomplished by
supplying a own RepositorySelector which uses certain values in MDC).
Therefore the file name within the
Would anyone have examples of how to use the DBAppender in the code
since there are none under the examples directory of the 1.3 alpha 6
release?
John
