Return-Path: Delivered-To: apmail-jakarta-turbine-dev-archive@apache.org Received: (qmail 30372 invoked from network); 11 Dec 2002 00:57:19 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Dec 2002 00:57:19 -0000 Received: (qmail 650 invoked by uid 97); 11 Dec 2002 00:58:33 -0000 Delivered-To: qmlist-jakarta-archive-turbine-dev@jakarta.apache.org Received: (qmail 630 invoked by uid 97); 11 Dec 2002 00:58:32 -0000 Mailing-List: contact turbine-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine Developers List" Reply-To: "Turbine Developers List" Delivered-To: mailing list turbine-dev@jakarta.apache.org Received: (qmail 618 invoked by uid 98); 11 Dec 2002 00:58:31 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DF68D0B.30100@apache.org> Date: Wed, 11 Dec 2002 01:55:39 +0100 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Turbine Developers List Subject: Re: [vote] plans for turbine 2.3 References: <1039460714.858.135.camel@enki> <3DF675C3.6030704@apache.org> In-Reply-To: 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 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Henning P. Schmiedehausen wrote: > Nicola Ken Barozzi writes: > > >>Look in the framework: >>http://cvs.apache.org/viewcvs/jakarta-avalon/src/java/org/apache/avalon/framework/logger/ > > >>AbstractLogEnabled.java >>AvalonFormatter.java >>ConsoleLogger.java >>Jdk14Logger.java >>Log4JLogger.java >>LogEnabled.java >>LogKit2AvalonLoggerAdapter.java >>LogKitLogger.java >>Logger.java >>NullLogger.java > > > Yep. Horrors. > That's exactly what I don't want in Turbine. The > logging code that I plan to check in has exactly 10 lines of code to > set up and replaces the whole LoggingService and lots of this "try to > log before we have something like LogService but switch to it after it > came up" horrors that spread all over Turbine and the Service Broker. I don't understand what your problem is, we have no problem in using it in many projects. Probably you were not doing it right, but I dunno actually what your code looked like. Remember that static loggers are hell in a server environment. The Component mus tuse the logger it gets from the container, period. Easy, clean, safe, and easily configurable. Try using Commons logging in a server environment with 10 apps all using it, and you'll see that you will start losing control on what's happening to the loggings. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: