Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 99835 invoked by uid 500); 2 Apr 2003 19:12:23 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 99803 invoked from network); 2 Apr 2003 19:12:23 -0000 Received: from smtp5.wanadoo.fr (HELO mwinf0201.wanadoo.fr) (193.252.22.29) by daedalus.apache.org with SMTP; 2 Apr 2003 19:12:23 -0000 Received: from anyware-tech.com (AToulouse-206-1-8-223.abo.wanadoo.fr [81.50.249.223]) by mwinf0201.wanadoo.fr (SMTP Server) with ESMTP id 73C103000374 for ; Wed, 2 Apr 2003 21:12:26 +0200 (CEST) Message-ID: <3E8B361B.7020704@anyware-tech.com> Date: Wed, 02 Apr 2003 21:12:27 +0200 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: fr, en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [proposal] deprecation logger References: <3E8B17F7.7030506@anyware-tech.com> <3E8B2D52.1090508@verizon.net> In-Reply-To: <3E8B2D52.1090508@verizon.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Vadim Gritsenko wrote: > Sylvain Wallez wrote: > >> Hi folks, >> >> We have in the 2.1 a number of features that are considered as >> deprecated, although still supported. We need a way to inform users >> (the ones that write Cocoon apps) that they use such deprecated >> features in a way that allows them to be found easily, and not >> intermixed in the usual logging flood. >> >> So I'm thinking about a global logger dedicated to deprecation >> messages. This would allow to write all messages going to that logger >> to e.g. a "deprecated.log" file. >> >> Now how do we make this logger accessible ? A static variable doesn't >> seem to be a good solution, so I'm thinking of adding it to the >> Avalon context. Any Contextualizable component can then access it. >> >> Thoughts ? > > > Nice suggestion; but can't we just use WARN for deprecation warnings? > In above-then-debug log setting these messages will be well noticable. Well, this is effectively much more simple ;-) But don't you think a special category getting all deprecation warnings could be useful ? Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }