Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 17448 invoked from network); 25 Mar 2010 13:55:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Mar 2010 13:55:59 -0000 Received: (qmail 66069 invoked by uid 500); 25 Mar 2010 13:55:58 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 65957 invoked by uid 500); 25 Mar 2010 13:55:58 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 65949 invoked by uid 99); 25 Mar 2010 13:55:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 13:55:58 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.158 is neither permitted nor denied by domain of yairogen@gmail.com) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 13:55:51 +0000 Received: from joe.nabble.com ([192.168.236.151]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NunX1-0000Gh-2Q for user@commons.apache.org; Thu, 25 Mar 2010 06:55:31 -0700 Date: Thu, 25 Mar 2010 05:55:31 -0800 (PST) From: yogen To: user@commons.apache.org Message-ID: <1269525331069-1690655.post@n4.nabble.com> Subject: How to use commons config in multiple VM environment MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am using commons configuration in a multi process and multi vm environment. Today, we have one config per process and this leads to a overload of duplicate parameters and a nightmare to maintain. Does anyone have best practices on how to unify the config, but still maintain flexibility for developers to test each process on its own in development lifer cycle? Thanks. -- View this message in context: http://n4.nabble.com/How-to-use-commons-config-in-multiple-VM-environment-tp1690655p1690655.html Sent from the Commons - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org