Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 728 invoked from network); 5 Jul 2008 14:29:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jul 2008 14:29:44 -0000 Received: (qmail 33909 invoked by uid 500); 5 Jul 2008 14:29:45 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 33886 invoked by uid 500); 5 Jul 2008 14:29:44 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 33875 invoked by uid 99); 5 Jul 2008 14:29:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Jul 2008 07:29:44 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of java4dev@gmail.com designates 209.85.134.191 as permitted sender) Received: from [209.85.134.191] (HELO mu-out-0910.google.com) (209.85.134.191) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Jul 2008 14:28:52 +0000 Received: by mu-out-0910.google.com with SMTP id w9so423133mue.0 for ; Sat, 05 Jul 2008 07:29:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=R/0G4FoAB8Lk6BtAbO0c/fRF+KN9/J34jw9j/wVfdWk=; b=Hhecs1etJSPcCP+Xdb8ysPh4qoWK56LeX3od7Av+NKDJcm+LpCkBUKYG68NOU9YQjk 08o6DxVoPJJhdMaXuYWOUS4RS4REbO1aLwQQhc4AmcagFKTz+9DYHUi+K7ktvFonXBP9 LI2DmYmQLmZtqeP+zZw9FMoW3VujSTRmlguiQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=vcUCpNXlNm8HBrSgozPbq0ix+cUSn3T/wBaZv51q7lajWU8vckfqNgFJI4R+vo0FsC eemjWYgvITo4vk+hmSlYVJWUT2hkS02e6zOSpRzCNu5+U5kCXA4nmBTfzZ4CFRJSpE1U 20UxPcWRogLIWSi5LGWT5oBxJpd6kPbwHm9Pw= Received: by 10.103.249.7 with SMTP id b7mr923871mus.51.1215268152420; Sat, 05 Jul 2008 07:29:12 -0700 (PDT) Received: from ?10.0.0.101? ( [62.1.229.2]) by mx.google.com with ESMTPS id y6sm6630917mug.15.2008.07.05.07.29.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 05 Jul 2008 07:29:11 -0700 (PDT) Message-ID: <486F84E8.6070003@gmail.com> Date: Sat, 05 Jul 2008 17:27:52 +0300 From: Java House Reply-To: java4dev@gmail.com User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: log4j-dev@logging.apache.org Subject: static logger Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello, I need to log in different files based on thread group. So I created my own RepositorySelector which supports exactly this scenario but in order for this to work I cannot have static Logger logger = Logger.getLogger("X"); because the last instance that is created is setting the logger object and this is not the desired result. I have to use Logger logger = Logger.getLogger("X"); but I have seen in so many places recomendations against such usage. How bad is it, to NOT use static logger; Considering the feature request would such a solution be acceptable; thank you --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org