Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 95825 invoked from network); 5 Apr 2005 02:14:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Apr 2005 02:14:25 -0000 Received: (qmail 79927 invoked by uid 500); 5 Apr 2005 02:14:20 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 79915 invoked by uid 500); 5 Apr 2005 02:14:20 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 79901 invoked by uid 99); 5 Apr 2005 02:14:20 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of qingtian.wang@gmail.com designates 64.233.184.199 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.199) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 04 Apr 2005 19:14:19 -0700 Received: by wproxy.gmail.com with SMTP id 71so1775039wri for ; Mon, 04 Apr 2005 19:14:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=lL1gGMhP89glkKMfcc8HhK+apvnoe7jwnKH9GrmCAnVpL+5tBBbw5vo8TgagTVc41janMIT2VtxOC0OnA+pN2YVC3KT7TImGHEOrUy9mJMGYQcV+x18r94iSZe23Sm1b8yblHsmZtj530iNi7PmmGD7MHT4bZp0GKJJ6qDix2Oc= Received: by 10.54.24.49 with SMTP id 49mr262531wrx; Mon, 04 Apr 2005 19:14:17 -0700 (PDT) Received: from ?192.168.100.102? ([24.13.36.72]) by mx.gmail.com with ESMTP id d7sm1322114wra.2005.04.04.19.14.16; Mon, 04 Apr 2005 19:14:17 -0700 (PDT) Message-ID: <4251F477.10309@gmail.com> Date: Mon, 04 Apr 2005 21:14:15 -0500 From: WANG Qingtian User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: Configuration - Reload Strategy in j2ee containers References: <4251B5FE.6080606@gmail.com> <4251BCD5.8050902@apache.org> In-Reply-To: <4251BCD5.8050902@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello Emmanuel, Thanks very much for the clarification! Can you also shed some light on the performance issue when the reloading mechanism is used versus when not used? Thanks again! Qingtian Emmanuel Bourg wrote: > Hello Qingtian, a reloading strategy is passive, it doesn't spawn a > thread to monitor the file, instead it checks if the file changed > everytime a property is accessed. So just use it as a replacement for > java.util.Properties. > > Emmanuel Bourg > > > WANG Qingtian wrote: > >> Hi, >> >> Is the reload strategy implemented by creating a thread that >> periodically checks the time stamp of the configuration file? If so, >> how do I make sure that thread is started/stopped properly when I use >> it in a j2ee container? Like, will the thread be killed when I shut >> down the web/ejb container? What is the "best practice" of using >> "configuration" in a j2ee container? >> >> Thanks a lot for your help!!! >> Qingtian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org