Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 68633 invoked from network); 25 Oct 2005 15:43:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Oct 2005 15:43:31 -0000 Received: (qmail 23365 invoked by uid 500); 25 Oct 2005 15:43:16 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 23285 invoked by uid 500); 25 Oct 2005 15:43:13 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 23138 invoked by uid 99); 25 Oct 2005 15:43:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2005 08:43:10 -0700 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_IN_SORBS_WEB X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [209.86.89.64] (HELO smtpauth04.mail.atl.earthlink.net) (209.86.89.64) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2005 08:43:08 -0700 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Sui/VUX0v7RyTdf6TlskP/tnVRVBQHquHG/arbmfiMuTjypPX8bMLpEVu0slEc/P; h=Received:Message-ID:Date:From:User-Agent:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [129.33.49.251] (helo=[9.37.214.129]) by smtpauth04.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1EUQwr-0007R5-6Q for user@geronimo.apache.org; Tue, 25 Oct 2005 11:42:49 -0400 Message-ID: <435E5273.7000408@earthlink.net> Date: Tue, 25 Oct 2005 11:42:43 -0400 From: Joe Bohn User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Geronimo User Subject: web applications and hosting containers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec79b2d428086cdfb2c10265e2e3bcf9fef1350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 129.33.49.251 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N The default Geronimo configuration includes both the Jetty and Tomcat web containers predeployed and started by default. Therefore, it would follow (when dealing with a web application that is not dependent upon any specific web container) that the web app would either: 1) upon a single deployment be capable of running in either a single, all, or any combination of containers. If this is the case then I expect that the container would somehow be specified when starting the application or the application would be started concurrently on all active containers (hence a runtime choice of container). 2) require the specification of a container(s) in the deploy command. The web app could then be deployed multiple times (once to each web container). The individually deployed applications could then be started independently on each container. However, it appears that there is no mechanism to reference a specific container from either the deploy command or the start command. How is the user supposed to interpret this? What behavior should the user expect when deploying and starting web applications that have no need for a container specific plan and hence include no geronimo deployment plan? To which container(s) are they deployed? Is the choice of the container a deployment decision (deploy command) or a run-time decision (start/stop command)? Thanks, Joe -- Joe Bohn joe.bohn@earthlink.net "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot