The straight JDBC implementation would be so simple to do, but I prefer not to bind everyone to using my database schema. Part of the beauty of using an O/R mapping tool (like OJB) is not having to hard-code my database name/column/etc.
I supposed I could get around it by pulling a few items from a resource file, but that would be reinventing some of what mapping frameworks already do.
Hi,
very interesting approach. I'm also looking forward to the "pure" JDBC-implementation.
Maybe they could be added to the commons-resources project, which is going to be used in Struts 1.2 as far as I remember.
http://jakarta.apache.org/commons/sandbox/resources/
Greetings,
Yann
The straight JDBC implementation would be so simple to do, but I prefer not to bind everyone to using my database schema. Part of the beauty of using an O/R mapping tool (like OJB) is not having to hard-code my database name/column/etc.
I supposed I could get around it by pulling a few items from a resource file, but that would be reinventing some of what mapping frameworks already do.
If you read about what you get by using OJB:
http://db.apache.org/ojb/features.html
Why would you want to do any of this from scratch?