You say about DDL generation that "Ebean does not support DDL generation from annotations and I personally have no interest in this idea. There are good tools to design and document a database and generate the DDL."
I chose Ebean instead of Hibernate for my application because it uses separated, detached client databases, and I wanted to ease my database access with an ORM tool but didn't need the complexity of Hibernate. I hesitated between ActiveObjects and Ebean but at the end I chose Ebean because it avoids using separate (duplicated) Entity beans, so it seemed more comfortable to use.
But then, a requirement for my application would be to have transparent updates as bugs are constantly fixed and slight changes are made. At updates, the client database structure may slightly change. Of course, the client who updates its application should not lose his own data so I need a solution that automatically updates the underlying database structure reflecting the applications needs without modifying existing data. It would be very nice if that would be possible to make with minimal extra effort needed.
I don't know how this task could be done with the tools you mention, and it seems a commonly needed task. Is there an external tool that is able to do it in a JPA compatible mode?
At the moment, it seems to me that I have two choices: Either I make this DDL generation tool myself, or I rewrite the application using ActiveObjects which - if I understood it correctly - supports this very task. I'm not quite sure yet which is the quicker approach (unfortunately I have no choice but using the quickest solution). But it would be a pity if I had to choose the latter as Ebean is great otherwise.
And then, if the first approach is the quicker, would you be interested in the result?