Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 78001 invoked from network); 25 Oct 2005 18:58:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Oct 2005 18:58:02 -0000 Received: (qmail 65544 invoked by uid 500); 25 Oct 2005 18:57:50 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 65482 invoked by uid 500); 25 Oct 2005 18:57:50 -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 List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 65470 invoked by uid 99); 25 Oct 2005 18:57:49 -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 11:57:49 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [66.163.169.225] (HELO smtp105.mail.sc5.yahoo.com) (66.163.169.225) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 25 Oct 2005 11:57:46 -0700 Received: (qmail 76589 invoked from network); 25 Oct 2005 18:57:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=SF9QefMBrGij6rJafkrnzZrTuurItqg8uLqXlva+U87SmfhRIMP7zvUWsVGd8KLRfzpMH3GInrJ96+A4ItF/xIpwT3ZhFtksR4JuDwat3IzPbvI1cQvDFY1oPy5PGrR9nw/YAwNWC5rkS9JTsTuQyGF7zqA3Dz11WVV+MhPon7Q= ; Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with plain) by smtp105.mail.sc5.yahoo.com with SMTP; 25 Oct 2005 18:57:26 -0000 Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: <200510251247.j9PCkucB030669@smtp-ft3.fr.colt.net> References: <200510251247.j9PCkucB030669@smtp-ft3.fr.colt.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2c16ed8d87a6c0907130192894843500@yahoo.com> Content-Transfer-Encoding: 7bit From: David Jencks Subject: Re: Geronimo configuration question Date: Tue, 25 Oct 2005 11:57:22 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.622) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Oct 25, 2005, at 5:46 AM, Vincent Massol wrote: > Hi, > > I'd like to add support for Geronimo in Cargo > (http://cargo.codehaus.org). > For that I need to understand how to configure Geronimo. > > In cargo we have 2 notions: > > - Standalone Configuration: This allows the user to tell where he'd > like the > container to be configured and a default working configuration is > created > for him/her at that location. > > - Existing Configuration: The user points to an already defined > configuration on his hard disk and Cargo uses it. > > I'd like to understand if it's possible to create a Standalone > Configuration > of Geronimo. To give you some examples for other containers: > > - On Tomcat, this means creating a directory containing the following > structure and then defining the catalina.home and cataline.base system > properties: > > Mytomcatconfig/ > |_ conf/ > |_ server.xml > |_ tomcat-users.xml > |_ web.xml > > - On WebLogic, this means creating an admin domain configuration > directory > structure > > - On JBoss this means creating a JBoss server configuration directory > structure > > - etc. > > It's actually of defining a base installation directory for the > container > and then separate the configuration from it. This allows leaving the > default > installation untouched. > > It also allows for example to run several instances of the same > container on > the same machine, all sharing the same base installation but having > different configurations. > > Is that possible? How would I do that? > We have a maven plugin to do this. See the unpackServer goal in plugins/geronimo-deployment-plugin/plugin.jelly. I'm not sure what your goal is with the sharing idea. Could you explain? Pretty much all the "per-server configuration" is now contained in var/config/config.xml (although the name of this file can be variable). This contains the list of configurations to be started and override values for gbean attributes. The name of the file to use is currently in a gbean attribute in the jar you start (server.jar, client.jar, deployer.jar). I've been planning to add a command line option to specify an alternate configuration file. Would this satisfy your needs for multiple "instances"? thanks david jencks