Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Date: Mon, 12 May 2003 10:31:49 -0700
Subject: Re: How to supress Axis logging?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: "'Lamkhede, Sudarshan (Cognizant)'" <LSudarshan@pun.cognizant.com>
To: axis-user@ws.apache.org
From: James Waldrop <sulam@well.com>
In-Reply-To: 
 <D464F551A951ED4E804B9713B519E6C9104C1A@NYC-EX101.doubleclick.net>
Message-Id: <9CE81FE0-849F-11D7-A366-003065D6314A@well.com>
Content-Transfer-Encoding: 7bit

On Monday, May 12, 2003, at 09:57  AM, Ekbote, Niranjan wrote:
> Secondly, I think the purpose
> was to selectively disable all Axis logging. That is I need a debug 
> log, but
> no log records from Axis into it. I don't think so you can do it using 
> a
> properties file.

The properties file I sent does that, unless I'm misunderstanding your 
point. It logs only INFO and higher level messages to the logfile from 
Axis, while another application is logging DEBUG messages. If you want 
to completely eliminate Axis messages you could simply set a null 
appender for the category, but personally I find getting WARN+ messages 
in my log is helpful, since it helps me debug serialization problems.

> And yes you can specify category levels using XML
> congifurator, infact I think XML based config files provide many more
> options than a simple properties file.

I'm certainly not trying to argue that properties files are better than 
XML -- you should configure Log4J however you like. I simply cut and 
paste the example from development I'm currently doing, since I believe 
it accomplishes the stated goal and does not involve writing custom 
filters.

James