Sorry, my last message went off prematurely. Here is the complete one.
As I understand it, the current *implementation* in Ant of event-based
model for logging does NOT fully take advantage of one of log4j's most
important advantages, that is, its ability to process and filter
messages by logger na
As I understand it, the current *implementation* in Ant of event-based
model for logging does NOT fully take advantage of one of log4j's most
important advantages, that is, its ability to process and filter messages
by logger name. This can be attributed partially to the way Log4jListener
is im
At 11:38 AM 1/9/2005, Vincent Massol wrote:
There is another solution: to use a custom logging monitor as explained here
(http://paulhammant.com/blog//000241.html) - I've done that for Cargo and it
looks good. I'm sure it is less powerful than using CL or UGLI but it has
the advantage of reducing t
Vincent,
Thanks for your quick response. It is much appreciated.
At 11:38 AM 1/9/2005, Vincent Massol wrote:
Hi Ceki,
Everything is open. However, I've never seen any issue WRT classloaders.
Maybe because I always force CL to use a specific implementation (instead of
letting it decide automatically
Hello,
In the log4j project, we need to perform integration tests between
log4j and various Application Servers. Sounds familiar? :-)
Our tests check that log4j correctly solves the "logging separation
problem" [1] when ContextJNDISelector is installed. Unfortunately,
since commons-logging relies
