Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@jakarta.apache.org Received: (qmail 13536 invoked by uid 500); 6 Jun 2001 13:21:58 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Avalon Development" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 13465 invoked from network); 6 Jun 2001 13:21:47 -0000 Message-ID: <3B1E2E16.55067EC5@apache.org> Date: Wed, 06 Jun 2001 09:20:22 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Avalon Development Subject: Re: Phoenix and Loggers References: <3B1E38FD.2A561A7C@benett1.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Charles Benett wrote: > > Hi! > > Updating James to use Logkit 1.0b2 I came across this scenario: a > component in a SAR that needs two loggers: one for 'functional' purposes > and one for security purposes (ie I want to be able to handle Access or > Authorization Exceptions differently than run of the mill stuff). > I was using Logkit.getLoggerFor(james.Security) but LogKit is now > deprecated. > > What is the best way to do this? > > Can I get a specified category from the Hierarchy objects in Phoenix? > > Would it be better to go: > > Logger securityLogger = getLogger().getChildLogger("security"); > and then use the server.xml file to plumb all the *.security loggers > together? Yep. That is preferred. Now, you can do the following: Hierarchy.getDefaultHierarchy().getLoggerFor("james.Security"); It is functionally the same as what the LogKit does. --------------------------------------------------------------------- To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: avalon-dev-help@jakarta.apache.org