Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 76375 invoked from network); 7 Aug 2004 12:23:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 7 Aug 2004 12:23:58 -0000 Received: (qmail 40510 invoked by uid 500); 7 Aug 2004 12:23:57 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 40448 invoked by uid 500); 7 Aug 2004 12:23:57 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 40430 invoked by uid 99); 7 Aug 2004 12:23:57 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.27.1) with SMTP; Sat, 07 Aug 2004 05:23:54 -0700 Received: (qmail 876 invoked by uid 65534); 7 Aug 2004 12:23:52 -0000 Received: from adsl-84-226-109-99.adslplus.ch (EHLO [192.168.1.10]) (84.226.109.99) by mail.gmx.net (mp014) with SMTP; 07 Aug 2004 14:23:52 +0200 X-Authenticated: #15507884 Message-ID: <4114C9F8.60309@gmx.ch> Date: Sat, 07 Aug 2004 14:24:24 +0200 From: Jakob Braeuchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.1) Gecko/20040707 X-Accept-Language: de, en MIME-Version: 1.0 To: OJB Developers List , Armin Waibel , Andrew.Clute@osn.state.oh.us Subject: Proposal to get rid of ojbConcreteClass Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N hi all, i think we need a more flexible approach when mapping multiple classes to one single table. today we have the field-descriptor 'ojbConcreteClass', a working solution i have to admit. the biggest problem is imo that we always store the name of the class in the database. this makes refactoring of the package structure unnecessarily difficult. another, but minor issue, is that ojbConcreteClass is an ordinary field-descriptor. i propose to add some kind of concrete-selector to the class-descriptor. this selector points to an ordinary field-descriptor. additionaly the selector may have a value that is stored instead of the real class name. if no selector-value is defined we could still use the class name as default: ... as an alternative the selector could also be defined using a special element: ... there's another proposal by andrew clute to include a class-selector in the reference-descriptor: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=ojb-dev@db.apache.org&msgNo=7861 actually this does not address the same problem, but we should make sure that the naming is consistent. what do you think ? jakob --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org