With struts1.1b2 I think you need to get another commons-logging.jar first.
If it can help, Struts will use your log4j conf file if it finds it. In this
conf file you need to set specifically org.apache.struts to have a log level
as WARN for example (as shirishchandra sakhare said!).
In your webapp init servlet, you will have something like this:
PropertyConfigurator.configure("path_to_your_log4j_conf_file");

and the conf file could look like this:

# Set root logger level to DEBUG and its only appender to A1.
log4j.rootLogger=INFO, A1
# A1 is set to be a ConsoleAppender.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{dd/MM/yy HH:mm:ss} %-5p %C{1}
%x - %m%n
log4j.logger.org.apache.struts=WARN

hope this helps.



-----Message d'origine-----
De : Matthew Meyer [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 30 janvier 2003 14:45
À : Struts Users Mailing List
Objet : Re: log4j problem


I am having a simmilar problem. I'm useing Struts 1.1b2 
within WTE 3.5. The digester and requestProcessor refuse 
to quit logging not matter what I set the log levels at. 
I'm guessing I'm just not finding the correct 
configuration file, but it's really getting annoying. 

Matt,

On Thu, 30 Jan 2003 11:09:10 +0100
  "De Cesco, Jonathan" <[EMAIL PROTECTED]> wrote:
>Hi all,
>I was using Log4J with struts1.0 with no problem. When I 
>updated to
>struts1.1b3, messages from Struts like "RequestProcessor 
>Processing a POST
>request for path url" are logged using my webapp log4j 
>configuration file.
>The problem is I don't want struts to log these messages 
>but it keeps using
>my log4J configuration once it finds it.
>anyone ????
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: 
>[EMAIL PROTECTED]
>For additional commands, e-mail: 
>[EMAIL PROTECTED]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to