No experience with EBean as such,
Yes, I was just evaluating different libraries for Db access in Java.
http://www.sienaproject.com/
and EBean are similar, Idea is to create a workflow from POJO to DB table.
Rest of the stuff in most of the app frameworks remain almost similar.
JOOQ is better because it gives an IDE based development aboost !
And I feel the way you are moving jooq with the feature set from all
possible frameworks , it will end up having most use cases in single library
!
Now Java+DB workflow becomes like this,
1) A framework for generating db structure from model classes { EBean,Play
Model layer, Siena Project,Hibernate ? !! }
2) A framework to automat db migrations {
https://github.com/azomazo/migrate4j , It is on SF but the one GitHub
supports Postgresql }
well version controlled model layer from step 1 can act as a fresh db setup
for specific version of the code.
3) A framework for fluent queries [ this is what we do most of the time ] :
JOOQ
Now the way model layer provides hot reloading in development mode { Play !,
and Siena does it } there has to be a hook from where we could generate JOOQ
artifacts too upon change in model layer ! { ask play ! community if it's
possible }.
