EJP is the next major release/fork of jPersist, and is a Java persistence framework. It is a trouble free, configuration and annotation free, framework based (as they all are) on JDBC. It is not a JPA implementation. It is much simpler and smaller (< 200K). The reason for the split is that EJP is not backwards compatible with jPersist, as EJP is far more advanced
and able to handle everything automatically. The good news is jPersist users will find switching trivial.
As most programmers realize, the definitions (xml/annotations) required of JPA/Hibernate are mostly needed for the purpose of schema generation, and not for mapping (even though both JPA and Hibernate require definitions for mapping). Since JDBC provides all the necessary metadata needed to figure out the mapping between objects and the database, these definitions aren’t actually needed unless in-code schema generation is needed.
Most of the time databases are created independent of the running application. In other words, the database team creates the database and/or you create the database, but you don’t create the database by running your application. This is also known as a separation of concerns, and is considered by many to be the best case.
If generating a schema “in-code” is what you need, then EJP is probably not going to work for you, since EJP doesn’t create the schema. However, If you simply want to connect to and use your database, EJP is perfect for you.
Connecting to your database with EJP is as simple as: