COPE

Cope with Object Persistence

COPE provides a persistence layer for Java. It makes application development faster compared to other persistent layers.

• No XML files need to be written, anything is easily specified within your java source code.
• No setting up of database tables - COPE does that for you.
• Transparent loading and writing of persistent objects.
• Easy-to-use search API for even complex queries providing type safety at compile-time.
• Complete isolation from the database, allows switching the DBMS instantly and eliminates SQL injection security vulnerability.
• Comes with a web application supporting the evolution of the persistent schema without loss of data.

COPE is open source software and available under the GNU Lesser General Public License. For getting started with COPE and as a template for your own projects there is a demo application available under the The MIT License.

Documentation is organized into trails, which show you how to use COPE on examples.

• Introduction Trail tells you how to get started with cope in your project.
• Field Trail tells you what kind of data can be stored using cope.
• Transactions Trail tells you how to use transactions in cope.
• Searching Trail gives you an introduction into the searching capabilities of cope.
• Field Reloaded Trail covers all the more specific possibilities to store data with cope not mentioned in the Field Trail.
• Web Application Trail shows you the little differences when using cope within a web container.
• Schema Trail shows you the schema evolution support of the COPE Console.

Additional information:

• API documentation
• Test Environments lists the enviroments COPE is tested on. It currently supports HSQLDB, MySQL, Oracle and PostgreSQL.

Downloads are hosted on sourceforge.

The development process of COPE is strongly influenced by the ideas of Extreme Programming. It heavily relies on Automated Continuous Integration.

Therefore, releases published on sourceforge do not carry any explicit version number. Instead each release is named after the build number assigned by the cruisecontrol server that built this release. Each build is subject to extensive automated unit testing on all supported databases (see Test Environments).