From dev-return-9491-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Sat Oct 23 06:48:03 2004 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 4391 invoked from network); 23 Oct 2004 06:48:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 23 Oct 2004 06:48:03 -0000 Received: (qmail 93912 invoked by uid 500); 23 Oct 2004 06:47:20 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 93843 invoked by uid 500); 23 Oct 2004 06:47:19 -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 93830 invoked by uid 99); 23 Oct 2004 06:47:19 -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; Fri, 22 Oct 2004 23:47:19 -0700 Received: by saturn.opentools.org (Postfix, from userid 500) id 9C2033EC0; Sat, 23 Oct 2004 02:47:17 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by saturn.opentools.org (Postfix) with ESMTP id 92DF5F5A8 for ; Sat, 23 Oct 2004 02:47:17 -0400 (EDT) Date: Sat, 23 Oct 2004 02:47:17 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@saturn.opentools.org To: dev@geronimo.apache.org Subject: Deployer Dependence on JSR-88 Message-ID: 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 So I was able to implement the first part of my deployment proposal -- splitting out the command-line processing from the Deployer GBean, and making it take advantage of JSR-88 where appropriate. Among other things, the deploy tool now figures out whether the server is already running (by checking for a live JMX connector) and can hot deploy (and start and stop) if the server is up. However, if I check this in, it will make the deployer depend on the JSR-88 API. There doesn't seem to be a good way around that, since we'd have to duplicate all the logic in the JSR-88 commands to get the same features without the API dependence -- and they are nice features. Still, I know compactness of the essentials is a goal. I could always split out a separate "J2EE deployer". That would have the advantage of dropping the need to handle some of the oddball arguments (mainClass, classPath, carFile) and making the implementation a little cleaner, but I'm not sure if having 2 deployers is really an advantage. Aaron