ok, moving this to [EMAIL PROTECTED]
No code yet, but once Torque generator has been decoupled, then it should be quite easy to implement what I have in mind.
And as I'm more familiar with Torque codebase (I have some 5-6 EJB applications in production with a patched version of Torque) it should be quite straightforward.
I'm especially interested in writing some migration tools for:
torque -> ojb/pb
torque -> hibernate
torque -> CMP entity beans 2.x
+ lower priority:
torque -> ojb/jdo
torque -> ojb/odmg
Why am I migrating away? Well, the static way of handling things (like Torque does currently) is causing me headaches in EJB world... And I have learned to prefer to keep my persistent bean classes as lightweight as possible...
As I really need this for my day job, I'm very much willing to write some implementation real soon.
Rgds,
Neeme
Martin Poeschl ::
we should start a discussion on [EMAIL PROTECTED] a general generator would be great! separating the torque generator is just a first stepdo you have some code to share?? martin Neeme Praks wrote:
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 <[EMAIL PROTECTED]>
Vastusesaaja: Jakarta Commons Developers List <[EMAIL PROTECTED]>
Adressaat: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
