if you are interested in my previous article “who need implemenation” ,there is a similiar project have already launched: Polyforms
it uses JPA and some annotation (very different from mines) to not implementing DAO layer.
hopefully I ‘ll make my first open source implemention next month 
wait for me
have fun
Hi again, a few hours ago I have read a question about ORM mapping for java . He wonders why and when this technology is chosen.
Disclaimer: I am omitting the case, when your database is just a storage for a CRUD apps. I am talking about complex applications, when stored procedures are used very extensively, like Oracle’s PL/SQL.
if you are working with more than one db vendor (mysql/postgresql/oracle ,vs…) both at the same project. you may like this a lot
the configuration sample below allow to run your hibernate application at two or more database vendors without changing any code Read more
I have changed the theme again
After reading an article of Martin Fowler about “Software Architects”: Who Need Architects? , I came to this point:
MOST IMPORTANT product of a Software Architect (SA) is The Prototype Project.
At least for some common patterns like DAOs.
As a popular manner, most of the java applications have at least three layers like UI, Service and DAO. For each layer you probably have interface and a single or more implementation classes. And while UI layer has some really complex businesses for effective UI experience, DAO layer is only related with CRUD operations for a single or a group of beans.
Here is the routine that you can get rid of
