Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 812 invoked from network); 4 Nov 2004 19:33:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Nov 2004 19:33:14 -0000 Received: (qmail 17922 invoked by uid 500); 4 Nov 2004 19:32:29 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 17795 invoked by uid 500); 4 Nov 2004 19:32:28 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 17765 invoked by uid 99); 4 Nov 2004 19:32:28 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [66.250.40.202] (HELO saturn.opentools.org) (66.250.40.202) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 04 Nov 2004 11:32:27 -0800 Received: by saturn.opentools.org (Postfix, from userid 500) id DF3923E5C; Thu, 4 Nov 2004 14:36:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by saturn.opentools.org (Postfix) with ESMTP id D7C5AF5CB for ; Thu, 4 Nov 2004 14:36:00 -0500 (EST) Date: Thu, 4 Nov 2004 14:36:00 -0500 (EST) From: Aaron Mulder X-X-Sender: ammulder@saturn.opentools.org To: dev@geronimo.apache.org Subject: Re: How to updated config.list during offline deployment In-Reply-To: <418A806C.5030700@gluecode.com> Message-ID: References: <418A806C.5030700@gluecode.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I'm working on the new deployer not the old one. As per the "proposed deployer syntax" message, this one actually offers a JSR-88 start method while the server is not running, which equates to updating the config list to include the module. I'd rather not start the server to do that... Also, the bulk of the feedback on the thread before that was that having two tools to handle deployment tasks was bad. Aaron On Thu, 4 Nov 2004, Jeremy Boynes wrote: > The other thing is that the --install option does just that - install > but not start (it is meant to be similar to JSR-88 distribute). > > I believe this can be better solved by adding an option to server.jar > that adds a new configId to the list to be run, something like: > > java -jar bin/server.jar --add my/new/config > > -- > Jeremy >