Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 10464 invoked from network); 1 Jul 2005 18:38:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Jul 2005 18:38:56 -0000 Received: (qmail 62172 invoked by uid 500); 1 Jul 2005 18:38:51 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 62137 invoked by uid 500); 1 Jul 2005 18:38: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 62123 invoked by uid 99); 1 Jul 2005 18:38:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 11:38:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.250.40.202] (HELO saturn.opentools.org) (66.250.40.202) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 11:38:52 -0700 Received: by saturn.opentools.org (Postfix, from userid 500) id D70AF3F28; Fri, 1 Jul 2005 14:39:18 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by saturn.opentools.org (Postfix) with ESMTP id D039EF342 for ; Fri, 1 Jul 2005 14:39:18 -0400 (EDT) Date: Fri, 1 Jul 2005 14:39:18 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@saturn.opentools.org To: dev@geronimo.apache.org Subject: CMP Field Mapping Required? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N It looks like our intention is that cmp-field-mappings are required in openejb-jar.xml. That is, a single schema sequence contains the table name and one or more cmp-field-mappings, which kind of implies that you can't leave out the cmp-field-mappings, though of course there's no way for us to force you (via the schema) to include one for each CMP field in ejb-jar.xml. Also, we do currently throw a deployment error if you forget a field. But I wonder whether this is all necessary. We could just default the column name to the CMP field name, so you would only need to provide the mapping if they were different. Likewise, we could default the table name to the ejb-name and make that optional too. What does everyone think about allowing defaults like that? I think it would be handy for trivial demos/examples, and unlikely to be used for real apps. All else being equal, I'm happy to support easy examples. But I'm not sure if people feel like explicit deployment errors would be better than using defaults if you try to map everything but forget one. Aaron