6.16.1 / January 19, 2016
|Size||1.8 MB (archived)|
Ebean has a simpler API than JPA. It achieves this through its 'Session Less' architecture. Ebean does not require a JPA EntityManager or JDO PersistenceManager and this removes the concepts of detached/attached beans and the issues associated with flushing/clearing and 'session management' of EntityManagers. This adds up to make Ebean's API much easier to learn understand and use.
Although Ebean has full ORM features (equivalent to JPA) it also has incorporated 'SQL/Relational' features. The idea being that many development efforts require control over the exact sql, calling stored procedures or are more simply solved with 'Relational' approaches. The ultimate goal for Ebean is to combine the best ORM features from JPA with the best 'Relational' features from products like MyBatis into a single persistence framework.
Ebean uses the same mapping as JPA with its @Entity, @Table, @OneToMany etc. annotations and xml. The mapping of Entity beans should be compatible between Ebean and JPA.
Going beyond JPA Ebean supports Java Generics and fetching "Partial" objects with its Query object.
// find customer by id Customer customer = Ebean.find(Customer.class, 1); // more complex query with joins List<Order> order = Ebean.find(Order.class) .fetch("customer") .fetch("customer.billingAddress") .fetch("customer.shippingAddress") .fetch("details") .fetch("details.product", "name") .where().eq("shipDate", today) .findList();