Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 6336 invoked by uid 500); 22 Mar 2003 05:05:40 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 6325 invoked from network); 22 Mar 2003 05:05:40 -0000 Received: from unknown (HELO eng.werken.com) (66.216.68.111) by daedalus.apache.org with SMTP; 22 Mar 2003 05:05:40 -0000 Received: from eng.werken.com (eng.werken.com [66.216.68.111]) by eng.werken.com (8.11.6/8.11.6) with ESMTP id h2M6MAd26232; Sat, 22 Mar 2003 00:22:10 -0600 Message-ID: <6303640.1048314130471.JavaMail.bob@eng.werken.com> Date: Sat, 22 Mar 2003 00:22:10 -0600 (CST) From: jira@codehaus.org To: dev@avalon.apache.org, peter@realityforge.org Subject: [jira] Commented: (PNIX-9) Extract logging from environment.xml Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Peter Donald Created: Sat, 22 Mar 2003 12:21 AM Body: Further details are available in message http://marc.theaimsgroup.com/?l=avalon-dev&m=104651163517039&w=2 Which contained: Ages ago (a year or two?) we decided that we wanted to separate out logging configuration from environment.xml - is this still desired? The reason is that I am currently documenting this and want to finalize the implementation prior to doccing it. The idea was to do something like SAR-INF/assembly.xml SAR-INF/config.xml SAR-INF/environment.xml SAR-INF/logging.xml and SAR-INF/logging.xml contains all the configuration for logging. I think it is just a case of no one getting around to doing it. This was just after Giacomo wrote the excalibur-logger package and we wanted to harmonize between Cocoon and Phoenix in this aspect. However I now have another motivation to do this. Several people have asked for support for log4j or native JDK1.4 logging configuration formats. So if we went the above way we could separate out logging we could search for configurations in the following order; SAR-INF/environment.xml (for backwards compatability) SAR-INF/logging.xml (excalibur logger) SAR-INF/log4j.xml (log4j xml format) SAR-INF/log4j.properties (log4j properties format) SAR-INF/log.properties (JDK1.4 format) That way people who want to use Log4j config files can do it easily. --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=PNIX-9 Here is an overview of the issue: --------------------------------------------------------------------- Key: PNIX-9 Summary: Extract logging from environment.xml Type: New Feature Status: Assigned Priority: Major Time Spent: Unknown Estimate: 0 minutes Project: phoenix Components: Log Manager Fix Fors: 4.1 Versions: 4.1 Assignee: Peter Donald Reporter: Peter Donald Created: Sat, 22 Mar 2003 12:17 AM Updated: Sat, 22 Mar 2003 12:17 AM Description: It has been suggested that we should extract logging definition from environment.xml and place it in a new file SAR-INF/log.xml This has been suggested because it mimics behaviour in other containers and logging can not really be considered to be part of the "environment" of an application. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org