Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 99769 invoked from network); 19 Jul 2002 11:08:18 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Jul 2002 11:08:18 -0000 Received: (qmail 3968 invoked by uid 97); 19 Jul 2002 11:08:32 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 3930 invoked by uid 97); 19 Jul 2002 11:08:31 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 3918 invoked by uid 98); 19 Jul 2002 11:08:30 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Content-Type: text/plain; charset="iso-8859-1" From: Peter Royal To: "Avalon-Phoenix Developers List" Subject: Re: New Alpha, Beta-Feature-Complete or just another nightly. Date: Fri, 19 Jul 2002 07:01:46 -0400 User-Agent: KMail/1.4.1 References: <3D37A9F7.6050403@yahoo.com> <200207191632.18368.peter@apache.org> In-Reply-To: <200207191632.18368.peter@apache.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200207190701.46321.proyal@apache.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Friday 19 July 2002 02:32 am, Peter Donald wrote: > On Fri, 19 Jul 2002 15:56, Paul Hammant wrote: > > Folks, > > > > Are we ready for the beta release? > > Probably not - still in middle of Peters work re configuration. Yup. There are two more features I would like to add before we go beta: * JMX enabling the ConfigurationValidator and FileSystemPersistentConfigurationRepository * Allow a hosted application to be "installed" but not "running" My goal? To be able to copy a SAR into apps/ that has incomplete configuration information. Phoenix starts it up, validates the config to see that it is incomplete, and leaves the app "installed" but not "running". Then via JMX (and eventually the mgmt console, which imho is orthogonal enough to be worked on while the core is in beta) one can fill in the missing config, to be stored in the FileSystemPersistentConfigurationRepository, validate what they have done, and then bring the app into a running state. I hope to have this done early next week, so a beta would not be far off :) -pete -- peter royal -> proyal@apache.org -- To unsubscribe, e-mail: For additional commands, e-mail: