Return-Path: Delivered-To: apmail-jakarta-log4j-dev-archive@www.apache.org Received: (qmail 21632 invoked from network); 22 Sep 2003 16:56:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Sep 2003 16:56:25 -0000 Received: (qmail 7665 invoked by uid 500); 22 Sep 2003 16:56:16 -0000 Delivered-To: apmail-jakarta-log4j-dev-archive@jakarta.apache.org Received: (qmail 7642 invoked by uid 500); 22 Sep 2003 16:56:16 -0000 Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@jakarta.apache.org Received: (qmail 7629 invoked from network); 22 Sep 2003 16:56:15 -0000 Received: from unknown (HELO pdxcorp1.vwsnet.com) (128.241.65.51) by daedalus.apache.org with SMTP; 22 Sep 2003 16:56:15 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message Subject: RE: Alternative contexts for MDC/NDC MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 22 Sep 2003 09:56:19 -0700 Message-ID: <984A7225EFC7FD44B0B66D3A29A14400048B65@pdxcorp1.vwsnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Alternative contexts for MDC/NDC Thread-Index: AcOA4PbvdsYh+Z6hSaOZmBpxIqF2AwASDhUw From: "Scott Deboy" To: , X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I agree we need support for this sort of cross-thread context information....properties which are inheritable through the logger hierarchy may fit the bill..I haven't looked into implementation details, but here's an example: If you got the "org.apache.log4j" logger and called 'setProperty("someprop", "someval"), then all loggers under org.apache.log4j would also have the property (you would also need support for removeProperty("someprop")). The property would be overridden if a closer ancestor set the property (if org.apache.log4j.net set the same property). Opinions dev folks? -----Original Message----- From: Thomas Muller [mailto:ttm@online.no]=20 Sent: Monday, September 22, 2003 1:09 AM To: log4j-user@jakarta.apache.org Subject: Alternative contexts for MDC/NDC=20 Log4j gurus, Does log4j have support for MDC/NDC across other contexts than threads? If not, is it any plans to implement this? For the time being I find my self having to prefix log messages with context sensitive information, and it doesn't really "feel" right at all. Any suggestions for a MDC/NDC framework allowing arbitrary contexts would be much appreciated, and also how to incorporate it into PatternLayout etc. -- Thomas ************************************************************************ * Copyright ERA Technology Ltd. 2003. (www.era.co.uk). All rights reserved.=20 The information supplied in this Commercial Communication should be treated in confidence. No liability whatsoever is accepted for any loss or damage=20 suffered as a result of accessing this message or any attachments. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: log4j-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: log4j-dev-help@jakarta.apache.org