Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 88025 invoked from network); 28 Apr 2006 14:09:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Apr 2006 14:09:20 -0000 Received: (qmail 57567 invoked by uid 500); 28 Apr 2006 14:09:09 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 57512 invoked by uid 500); 28 Apr 2006 14:09:08 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 57484 invoked by uid 99); 28 Apr 2006 14:09:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 07:09:07 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of Greg.Monroe@dukece.com designates 65.112.55.73 as permitted sender) Received: from [65.112.55.73] (HELO mail.dukece.com) (65.112.55.73) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 07:09:07 -0700 Received: from dukece-mail3.dukece.com ([192.168.1.222]) by mail.dukece.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Apr 2006 10:09:04 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Plan to enhance Database Mapping info Date: Fri, 28 Apr 2006 10:08:45 -0400 Message-ID: <8F5843B903F59D4C8C6806BB49A39119062A6E@dukece-mail3.dukece.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Plan to enhance Database Mapping info Thread-Index: AcZpyJnJlZPulCX3THix8KZpFS/SigA/mo3A From: "Greg Monroe" To: "Apache Torque Developers List" X-OriginalArrivalTime: 28 Apr 2006 14:09:04.0421 (UTC) FILETIME=[4E7BBD50:01C66ACD] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Thomas Vandahl [mailto:thomas.vandahl@tewisoft.de]=20 >=20 > Please keep in mind that the Avalon interface=20 > (Torque/TorqueComponent) should be updated as well. In digging into the code some more, I probably won't add the methods to the Torque class. Instead, I'll just add an=20 initialize() method to the DatabaseMap class. This means that not interfaces will need to be updated. More on this when I answer Thomas F's note. >=20 > What about the managers? Maybe I'm the only one who uses JCS caching,=20 > but I would love to see them considered... >=20 > This would require some getManager() method in all objects and=20 > getOmClass(), getPeer() and getTableMap() in the managers. Good point and the reason to run this by everyone first. Once=20 again, more on this in the next note. >=20 > Just one question for my understanding. Why do you need special=20 > introspection code if you can have Beans generated? Could you=20 > give some example where this is useful? In my particular case, I'm looking at having some generic XML=20 import and export code that uses the Torque generated schema DTD.=20 For the import case, as the XML file is parsed, the element and=20 attribute tag strings have to be mapped into the Torque objects that will be populated and saved. Since I want it to be generic=20 so that no code has to be changed as tables and columns are added or modified, I need a fully populated map structure find this=20 info. In the export case, I want to generate the proper element and=20 attribute tags from a (possibly mixed) List of objects generated by application specific code. So I have to be able to inspect each object on the list and find the matching strings that identify it in the XML output file. Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are = confidential communication or may otherwise be privileged or = confidential and are intended solely for the individual or entity to = whom they are addressed. If you are not the intended recipient you may = not rely on the contents of this email or any attachments, and we ask = that you please not read, copy or retransmit this communication, but = reply to the sender and destroy the email, its contents, and all copies = thereof immediately. Any unauthorized dissemination, distribution or = copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org