This page highlights the new features and changes introduced in 3.0 release, roughly corresponding to the latest released milestone. It is a high level overview and as such is by no means complete. Consult RELEASE-NOTES.txt file included in each release for the full list of changes.
Distribution Contents Structure
- There are a few changes in the contents of the distribution "lib" folder. For details see this page. Main Cayenne JAR is now called "cayenne-server-x.x.x.jar". We no longer ship the "fat" jar with dependencies. Instead dependencies are included in the separate jars in "lib/third-party" distribution folder.
- CayenneModeler is located in the "bin" folder. Never mind the "lib/cayenne-modeler-x.x.x.jar" - this is just an underlying Modeler library, used in "local JNDI" configuration for instance, not the runnable application.
Cayenne JPA Provider
(status: preview)
Cayenne 3.0 includes an in-progress partial implementation of a Java Persistence API specification
compliant persistence provider, with support for POJO and JPA annotations. Provider can be used in a standalone mode, as well as a part of a J2EE container.
Currently implemented features:
- Provider, EntityManagerFactory, EntityManager API bridge to the current Cayenne stack
- Loading mapping from annotations
- Loading mapping from XML
- Class enhancement
- Field-based access and property-based access
- EJBQL
- Entity callbacks
- All types of relationships and simple properties
- Embeddables
- Single table inheritance
Object Relational Mapping
Killed DerivedDbEntity Concept
Stopped supporting DerivedDbEntity - its functionality (aggregate queries) is achieved via EJBQL and other means.
Embeddables
(as of M4 there's no Modeler support)
Added a new mapping artifact - Embeddable, that allows to map composite objects to a single table.
Flattened Attributes
(as of M4 there's no Modeler support)
Just like with "flattened" relationships, now there is a way to map an ObjAttribute that spans one or more DbRelationships and is mapped to a column of a joined table.
Persisting Primitives and a Number of Other Simple Properties
DataObjects are now allowed to have primitive properties, such as int, boolean, etc. Also Cayenne can now persist the following extra simple property types: java.util.Calendar, java.math.BigInteger, java.io.Serializable, char[], java.lang.Character, java.lang.Character[], java.lang.Byte[].
Support for To-Many Relationship Maps and Collections.
In addition to mapping a to-many relationship as a List, Cayenne now supports to-many Maps (keyed by target object pk, or an arbitrary unique property), Sets and generic Collections. Note that relationship maps is the only conceptually new type of relationships. Collection and Set are not that different from the earlier List behavior (that was a Collection, and just like Set ensured uniqueness of its objects).
Support for "extended" Enums Mapping
In addition to vanilla Java enums, Cayenne allows enums to provide a custom database value for each enumerated instance by implementing org.apache.cayenne.ExtendedEnumeration. This way a persistent value doesn't have to be tied to the enum Java name or position.
DbAttribute Scale and Precision
Changed DbAttribute "precision" property to "scale" (as it meant scale all along) and added a separate "precision" attribute to track precision.
Cayenne Persistence API
Many of the improvements below were done to support the JPA provider, still Cayenne applications can take advantage from all of these things without using JPA.
Java 5 Migration
Cayenne now requires Java 5 or newer to run. This allowed us to start using generics, enums and other Java 5 features.
ObjectContext
While you can still use DataContext directly, we encourage you to avoid direct dependency on DataContext throughout your code, and instead use org.apache.cayenne.ObjectContext interface. E.g.:
ObjectContext context = DataContext.createDataContext();
This protects your code from the evolution of the underlying implementation, allows you to customize context behavior by using interface wrappers. There are plans to update all Cayenne API to return ObjectContext everywhere DataContext might be returned.
EJB QL Queries
(as of M3 there's no Modeler support)
Never mind the "EJB" in the name. EJBQL queries are a powerful object query mechanism borrowed from the JPA specification and added to Cayenne API. EJBQLQuery is a first-class citizen, just like SelectQuery.
SQLTemplate Query Improvements
Entity Lifecycle Callbacks
Just like EJBQL, lifecycle callbacks is a JPA-inspired feature that allows to perform custom operations at certain points in the object lifecycle. For more details see this page.
General Query Improvements
- Added support for fetch offset (complimentary to the existing "fetch limit").
DataContext Changes
Implemented DataContext.rollbackChangesLocally(). This was missing in 2.0, limiting the operation of the nested DataContexts.
Cache Management
Expression Improvements
- Added missing DB expressions to ExpressionFactory.
- Added support for OUTER JOINS
- Added support for matching against TRUE and FALSE.
Database Integration Changes/Improvements
- Added support for "long" primary keys (vs. "int" PK used previously)
- Added adapter for SQLite
database.
- Added adapter for H2
database.
- Added stored procedure support on MySQL.
- Changed default table type on MySQL to InnoDB, added MySQL FK constraints support in the Modeler.
- Turned on update query batching on SQL Server and Derby.
Class Generation Improvements
- Generating classes for DataMaps that contain type-safe methods for all mapped SelectQueries.
Prefetching Improvements
- Joint prefetches are switched to OUTER joins, removing the major limitation to their use.
POJO Persistence
(status: preview)
- Implemented class enhancer to enhance POJO's into org.apache.cayenne.Persistent
Remote Object Persistence
Validation callbacks support for ROP ObjectContext.
Now object validation works the same way on the ROP client as it did on the server.
CayenneModeler
The Modeler underwent significant changes with the goal to improve usability and look-and-feel.
- Added copy/paste support
- Reworked ObjRelationship mapping dialog
- Added combo auto-completion
- Added a usable and good looking welcome screen
- Added contextual menus
- Added detection of project file changes on disk
- Added multi-item selection
- Added ability to specify password encryption mechanism
- Added ability to drag and drop cayenne.xml from the filesystem to the Modeler window to open the project.
- Added support for to-many relationship collections mapping.
- Added "search" functionality
- Added lifecycle callback and listener mapping functionality.
- Added support for merging DataMap changes back to the database.
- Removed support for DerivedDbEntity
- Added confirmation dialog for delete actions
- Reopen Last Project on Startup
- Added progress/log view
- Added SQL syntax highlighting.
Deployment and Runtime
Improved Performance
- Paginated query algorithm is changed, resulting in very significant performance improvements on large data sets (this also improves ROP paginated query performance). This includes faster query times and much smaller memory footprint of an unresolved list.
- Reduced the scope of lock on a shared cache during commit, that should result in improved concurrency.
- ROP new context creation speed is improved, as EntityResolver is cached on the client after first retrieval.
- ROP uses a "diff compression" algorithm on commit, reducing the amount of data passed around.
Improved Memory Management
- Leak free ObjectContext
- Query lists are cached in an LRU map, so there's no indefinite memory growth when using query caching.
Logging Switched to commons-logging from Log4J
Cayenne no longer has a Log4J dependency. Instead it uses Jakarta commons-logging, as described here. Note that 2.0 Log4J configurations should continue to work, although now it is a user responsibility to bootstrap Log4J - Cayenne will no longer do it for you. E.g. you can do this on startup:
org.apache.log4j.PropertyConfigurator.configure("cayenne-log.properties");
Tools
- Switched "cgen" to "version 1.2" of the template as a default version
- Support for classpath in "cdbgen".
.