From log4j-dev-return-12332-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org Thu Apr 20 20:06:05 2006 Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 23542 invoked from network); 20 Apr 2006 20:06:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Apr 2006 20:06:04 -0000 Received: (qmail 78475 invoked by uid 500); 20 Apr 2006 20:06:01 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 78373 invoked by uid 500); 20 Apr 2006 20:06:01 -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 78266 invoked by uid 99); 20 Apr 2006 20:06:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2006 13:06:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of boris.unckel.mlg@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 20 Apr 2006 13:06:00 -0700 Received: (qmail invoked by alias); 20 Apr 2006 20:05:38 -0000 Received: from i5387D309.versanet.de (EHLO [192.168.0.2]) [83.135.211.9] by mail.gmx.net (mp030) with SMTP; 20 Apr 2006 22:05:38 +0200 X-Authenticated: #143822 Message-ID: <4447E98D.2080306@gmx.net> Date: Thu, 20 Apr 2006 22:05:33 +0200 From: Boris Unckel User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Log4J Developers List Subject: Re: 1.3-alpha8 - Extending TimeBasedRollingPolicy References: <21BC71BEAB43B04A95E5DB95AC7FA1EB026ED139@auntm202.apac.corp.eds.com> In-Reply-To: <21BC71BEAB43B04A95E5DB95AC7FA1EB026ED139@auntm202.apac.corp.eds.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello Lyall, Pearce, Lyall wrote: > I am unsure if this is more a user or developer question, I will lean > towards developer unless told otherwise. > > > log4j1.3-alpha8 has a nice class TimeBasedRollingPolicy > (http://logging.apache.org/log4j/docs/api-1.3/org/apache/log4j/rolling/T > imeBasedRollingPolicy.html) > > The Primary question: Why are the classes marked final? Why can't I > extend a log4j class? I am not a log4j developer. I have seen the discussions about compatibility on this list for the development of log4j 1.3 and the enormous efforts spend on compatibility. It is very hard to change the internal implementation of an class if lots of people are extending it and relying on a specific behaviour. If you want to have your homegrown XYZPolicy: Copy the code, implement the interface and use it. If log4j developers want to change something, they just have to care that the interface is not broken, but they can change the other class without braking anyones code. Regards Boris --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org