I find that the MapBean is great for quick value pair access.
I do prefer, in addition to this, to have arbitrary sql mapped to java Classes; classes that are not already mapped as entity beans. And indeed the class attributes can be primitives only.
The thing is that for reporting and analysis or quick dirty data reads I just have to come up with ad hoc sql and using a MapBean will be as useful as jdbc but not more.
The value of Ebean is the freedom you gain to explore outside the accepted standard, for convenience or esoteric purposes.
Thanks for a great job.