Hi!
I'd like to know the easiest way of customizing the format of printed
exception stacks.
I need a special format for exceptions of specific types.
I tried to subclass ConsoleAppender and overwrote the subAppend method. This
works quite well. But if I choose later to use the RollingFileAppende
This was discussed as late as yesterday on [EMAIL PROTECTED] See
http://marc.theaimsgroup.com/?t=10632404602&r=1&w=2
In short, in log4j 1.3 you will be able to instruct PatternLayout to use
your own stack tracing functionality.
At 09:44 AM 9/12/2003 +0200, HANDSCHMANN Robert wrote:
Hi!
I'd
If I want to "warn" for all apache projects, but then override that
setting for Velocity - is the following syntax correct? It doesn't seem
to be working, that's why I ask:
In my velocity.properties file, I have:
runtime.log.logsystem.class=org.apache.velocity.
Hi,
I am trying to get log4j to work in the following environment;
tomcat 4.1.27 log4j 1.2.8 struts 1.1
I have been able to get it working through invoking tomcat through
JBuilder. However when I run it with the startup.bat file I get a
weird error. I have a log4j.xml file that works fine in
- Are you compiling log4j yourself using JBulder?
- Do you have older versions of log4j lying around?
At 02:57 PM 9/12/2003 -0500, you wrote:
Hi,
I am trying to get log4j to work in the following environment;
tomcat 4.1.27 log4j 1.2.8 struts 1.1
I have been able to get it working through invo
The level values are seem OK.
However, no need to have an appender-ref in each logger. Appenders are
inherited cumulatively.
I assume an appender named CONSOLE is defined somewhere... right?
At 06:32 AM 9/12/2003 -0600, Matt Raible wrote:
If I want to "warn" for all a
We are using log4j 1.2.8. in our project (J2EE on WLS server). We have
sub-classed the Logger and LoggerFactory according to the examples. We are
using
an XML file for configuration.
When we use or (without the class attribute) and
in our log4j.xml, the DOMConfigurator is creating Logger
in
Hi,
The bug that you are referring to has not been resolved. You can try the work-around
that I posted in http://marc.theaimsgroup.com/?l=log4j-user&m=106312777504479&w=2.
That worked for me and now the loggers returned by Logger.getLogger(class) are my
Logger subclasses.
Here is the basic