Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 6371 invoked from network); 12 Dec 2002 18:37:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Dec 2002 18:37:15 -0000 Received: (qmail 1775 invoked by uid 97); 12 Dec 2002 18:38:16 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 1730 invoked by uid 97); 12 Dec 2002 18:38:14 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 1693 invoked by uid 98); 12 Dec 2002 18:38:14 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Thu, 12 Dec 2002 18:36:08 +0000 Subject: Re: [logging] Adding jndi java:env support Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: robert burrell donkin To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <94708C12-0E00-11D7-B2A8-003065DC754C@blueyonder.co.uk> X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N sounds like a good plan. this sounds (to me) like a change big enough to call for a new (major?) version. (i'm not a cvs expert) but from what i can see there have been some small changes since the last release. maybe a quick bugfix 1.0.3 release would be a good idea before adding making this change. - robert On Thursday, December 12, 2002, at 03:29 AM, Costin Manolache wrote: > Based on Ceki's email - I think it would be a good idea to add > this mechanism in the default logging factory. > > My proposal is to insert a lookup for > > java:comp/env/CommonsLoggingFactory > > at the top of the discovery chain. If such a factory exists, it'll > be used to create the logger. If not, we'll continue with the > normal mechanism. > > The big downsize is that we'll add a compile dependency on > JNDI ( the code can catch ClassNotFound - and run even if > JNDI is not present ). > > This will allow containers using commons-logging to better enforce > isolation between apps. > > In addition, I think we should add an optional "domain name" prefix. > If such a prefix is set ( for example in > java:comp/env/CommonsLoggingDomain) > then it'll be added in front of every log name that is created. > > For example, if the container will set myHost:8080/myApp/ as a prefix, > logs created in that app will be named: > myHost:8080/myApp/org.apache..... > > > As a note, web.xml allows you to define and set a number of > jndi entries. This could also be used to allow user-based tuning, > but in general the container settings should be able to > take preference . > > Costin > > > > > -- > To unsubscribe, e-mail: org> > For additional commands, e-mail: org> > -- To unsubscribe, e-mail: For additional commands, e-mail: