Future Directions for Ebean

Future Directions Long Term Medium Term Short Term
Long Term JPA Implementation It makes sense to be able to utilize Ebean via the standard JPA interface. This means the implementation of an EntityManager and EJBQL etc.
Medium Term JDBC4 Review JDBC4 for additional features that would be potentially useful. Of special interest would be the XML support and how this would be used and API changes. SQL3 Support for using database inheritance (SQL3 and Postgres) should be added with the other inheritence strategies. There maybe other SQL3 features that people wish to have better support for.
Short Term Inheritance strategies Currently Ebean supports Inheritance via the 'Single Table Strategy'. Support for 'Table per Concrete Class' and 'Joined Table per subclass' needs to be added. In addition support for using SQL3 Type Inheritance should also be added and this probably makes sense to do at the same time. Documentation Ebean javadoc is in reasonable shape but there is a need for more general documentation. Explanation on how things actually work and perhaps code examples. Default support for more Databases Add to the list of vendor databases that get configured automatically. DB2, HSQL and Postgres would be top of my list.