Return-Path: Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 25105 invoked from network); 10 Feb 2003 12:34:25 -0000 Received: from mail.hot.ee (HELO hot.ee) (194.126.101.94) by daedalus.apache.org with SMTP; 10 Feb 2003 12:34:25 -0000 Received: from localhost (relay1 [127.0.0.1]) by hot.ee (Postfix) with ESMTP id 8C2EBA9ACC for ; Mon, 10 Feb 2003 14:34:25 +0200 (EET) Received: from hot.ee ([127.0.0.1]) by localhost (relay1.hot.ee [127.0.0.1:10024]) (amavisd-new) with ESMTP id 13888-10 for ; Mon, 10 Feb 2003 14:34:25 +0200 (EET) Received: from apache.org (80-235-55-108-dsl.kjj.estpak.ee [80.235.55.108]) by hot.ee (Postfix) with ESMTP id E515EA9B70 for ; Mon, 10 Feb 2003 14:34:24 +0200 (EET) Message-ID: <3E479C50.7040808@apache.org> Date: Mon, 10 Feb 2003 14:34:24 +0200 From: Neeme Praks User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; et-EE; rv:1.2.1) Gecko/20021130 X-Accept-Language: et MIME-Version: 1.0 To: Turbine Torque Developers List Subject: Re: separate torque generator References: <3E478954.5020607@marmot.at> In-Reply-To: <3E478954.5020607@marmot.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by mail.hot.ee X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'm currently thinking about implementing some more general generator... See my email to commons-dev below. Would this fit inside this decoupled generator better? -- Algne kiri -- Original Message -- Teema: [sql] DAO pattern? Kuup�ev: Fri, 07 Feb 2003 01:51:29 +0200 Kellelt: Neeme Praks Vastusesaaja: Jakarta Commons Developers List Adressaat: commons-dev@jakarta.apache.org http://java.sun.com/blueprints/patterns/DAO.html I would be interested in implementing the DAO pattern for commons-sql: * based on database schema, generate: * bean interfaces * simple bean implementations (private fields, getters and setters) * optionally also abstract classes for entity beans (v2) * based on some query descriptor, generate: * factory interfaces * factory implementations: OJB,Torque,hibernate,entity beans v2... This would allow people to use more-or-less pluggable persistence APIs. I'm currently considering converting by applications from Torque to OJB, so I'm probably going to implement this anyway... Would this be in the scope of the commons SQL project? As this is kind of persistence abstraction (e.g. commons-logging), then I guess it seems to be a fit for commons, no? Any pointers are helpful, as there seems to be zero docs available currently (only docs I could find were copy-paste from torque). I saw that there are a bunch of jelly scripts for DDL generation, but how do they actually integrate with the rest of the stuff and how do I invoke them...? Rgds, Neeme Martin Poeschl :: > i want to separate torque's generator from the runtime environment > > here's the plan: > > o move all generator stuff to /src/generator > (incl. dtd, templates, maven-plugin, ...) > > o maven build for the generator > > o adopt the runtime tests to use the torque-gen.jar > > o move the generator related xdocs to src/generator/xdocs > > > maybe we can use the generator as basis for a more general generator > we could also switch to use commons-sql for the sql-generation > > i'll add a PRE_GENERATOR tag to the repo before i'll checkin the changes > > martin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org > For additional commands, e-mail: torque-dev-help@db.apache.org > >