Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 31891 invoked from network); 22 Aug 2005 15:30:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2005 15:30:34 -0000 Received: (qmail 22420 invoked by uid 500); 22 Aug 2005 15:30:32 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 22212 invoked by uid 500); 22 Aug 2005 15:30:31 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 22191 invoked by uid 99); 22 Aug 2005 15:30:31 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2005 08:30:30 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id D6CAB122; Mon, 22 Aug 2005 17:30:29 +0200 (CEST) From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 35529] - [configuration] FileChangedReloadingStrategy javadoc misleading X-Bugzilla-Reason: AssignedTo Message-Id: <20050822153029.D6CAB122@ajax.apache.org> Date: Mon, 22 Aug 2005 17:30:29 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35529 ------- Additional Comments From jordanh@zootweb.com 2005-08-22 17:30 ------- Spawning a thread would probably violate the j2ee spec and cause huge problems for people who use containers like JBoss. Having a true monitoring solution would be really nice though. What does the 5000 ms rate actually do if not monitor the file every 5 seconds? I to found the javadoc incredibly confusing. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org