Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 86586 invoked from network); 3 Aug 2005 05:48:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Aug 2005 05:48:38 -0000 Received: (qmail 55104 invoked by uid 500); 3 Aug 2005 05:48:31 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 55053 invoked by uid 500); 3 Aug 2005 05:48:31 -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 55039 invoked by uid 99); 3 Aug 2005 05:48:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2005 22:48:31 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [72.10.34.3] (HELO ss53.shared.server-system.net) (72.10.34.3) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2005 22:48:21 -0700 Received: from [127.0.0.1] (c-24-4-205-190.hsd1.ca.comcast.net [24.4.205.190]) (authenticated bits=0) by ss53.shared.server-system.net (8.12.11/8.12.11) with ESMTP id j735mRBO009844 for ; Tue, 2 Aug 2005 22:48:28 -0700 Message-ID: <42F05AAB.5050807@toolazydogs.com> Date: Tue, 02 Aug 2005 22:48:27 -0700 From: "Alan D. Cabrera" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: Naming schema "port" elements References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 8/2/2005 5:19 PM, Aaron Mulder wrote: > So our our naming schema, when dealing with web services, has an >unfortunate overlap with two different "port" elements that are subtlely >different: > > > > > > (def #1, portCompletionType) > (contents of port #2) > > > > (def #2) > ... > > > > In other words, the first "port" element contains all the same >stuff as the second "port" element plus one extra element. > > I think it would be preferable to have what's currently the first >"port" look like this: > > > > > > > That way both "port" elements would be identical. > > Any objections to making this change in M5? > > > Nope. Regards, Alan