Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 26694 invoked from network); 21 Feb 2006 11:51:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Feb 2006 11:51:07 -0000 Received: (qmail 37686 invoked by uid 500); 21 Feb 2006 11:51:05 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 37657 invoked by uid 500); 21 Feb 2006 11:51:04 -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 37642 invoked by uid 99); 21 Feb 2006 11:51:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2006 03:51:03 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_00_10,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of dccarew@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO pproxy.gmail.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2006 03:51:03 -0800 Received: by pproxy.gmail.com with SMTP id 57so1412952pya for ; Tue, 21 Feb 2006 03:50:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ewspHYhEEWPoL10BZxH8+XvWUpN0wQApW0BoNq+f5Z5begD1TKrvebTm/iDvjV64Kue7nXKZJtG3SC2L8gn0WIKqBzHODgbRRKcS5GKKPWkshE9sDzyk1bbSxRaSt21A/h4BlQDbCt4EpUc9Nk9JkWYP+vZoIGHYa1NUG6hS51A= Received: by 10.35.99.17 with SMTP id b17mr1731613pym; Tue, 21 Feb 2006 03:50:42 -0800 (PST) Received: by 10.35.88.5 with HTTP; Tue, 21 Feb 2006 03:50:42 -0800 (PST) Message-ID: <419beb980602210350h6045e4dcpa31201a47c325f98@mail.gmail.com> Date: Tue, 21 Feb 2006 05:50:42 -0600 From: "David Carew" To: user@geronimo.apache.org Subject: Any naming conventions in deployment plans for module configIds ? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6670_5563672.1140522642771" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_6670_5563672.1140522642771 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I've seen ModuleName/ModuleName a lot for standalone modules. What about modules in an .ear ? Is the convention then EARModuleName/ModuleName or is there really no naming convention yet ? thanks ------=_Part_6670_5563672.1140522642771 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I've seen  ModuleName/ModuleName a lot for standalone modules. What ab= out modules in an .ear ? Is the convention then EARModuleName/ModuleName or= is there really no naming convention yet ? thanks
------=_Part_6670_5563672.1140522642771--