As also described in the Hibernate book from King and Bauer: "With the adoption of Java™ 5 generics, the idea of a generic typesafe Data Access Object (DAO) implementation has become feasible. In this article, system architect Per Mellqvist presents a generic DAO implementation class based on Hibernate. He then shows you how to use Spring AOP introductions to add a typesafe interface to the class for query execution."
Tokyo Cabinet is a library of routines for managing a database. The database is a simple data file containing records, each is a pair of a key and a value. Every key and value is serial bytes with variable length. Both binary data and character string can
jLynx is a simple, lite, hi-performance layer over the JDBC API. Persist and retrieve POJO and Map objects directly. Designed for developer productivity. Simpler, easy to learn, easy to configure as compared to Hibernate, JPA, etc.
jLynx generates JavaBean objects based on your database schema. For example if you have 24 tables and views in your database, jLynx will create 24 objects with properties that map to the field names in each table. The jLynx Generator creates the objects and compiles them. You can also use the generated source instead if you prefer to customize the objects. Using the API to persist objects is trivial.
jLynx Framework implements the Relational interface, which has all necessary methods to persist objects and fetch entire collections of objects.
jLynx leverages the strengths of SQL and the strengths of Java without having to write/maintain J2EE code. It is truly the best of both worlds.
Reflection is a programming language technique that achieves dynamic adaptability. It can be used to reach aspect –or any kind of application– adaptation at runtime. Most runtime reflective systems are based on the ability to modify the programming la
HiberObjects is an Eclipse plugin for object oriented design of classes and unit tests for Java Persistence API or Hibernate. PropertyChange support and DTO's for Google Web Toolkit (GWT) can also be generated.
Hibernate is a powerful, high performance object/relational persistence and query service. Hibernate lets you develop persistent classes following object-oriented idiom - including association, inheritance, polymorphism, composition, and collections. Hibernate allows you to express queries in its own portable SQL extension (HQL), as well as in native SQL, or with an object-oriented Criteria and Example API.
jPersist is an extremely powerful, light-weight, object-relational database persistence API that manages to avoid the need for configuration and annotation; mapping is automatic. jPersist uses JDBC and can work with any relational database and any type of connection resource. jPersist uses information obtained from the database to handle mapping between the database and Java objects, so mapping configuration is not needed, and annotation is not needed, in fact there is no configuration needed at all.
About XStream
XStream is a simple library to serialize objects to XML and back again.
Features
* Ease of use. A high level facade is supplied that simplifies common use cases.
* No mappings required. Most objects can be serialized without need for specifying mappings.
* Performance. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput.
* Clean XML. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization.
* Requires no modifications to objects. Serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor.
* Full object graph support. Duplicate references encountered in the object-model will be maintained. Supports circular references.
* Integrates with other XML APIs. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML).
* Customizable conversion strategies. Strategies can be registered allowing customization of how particular types are represented as XML.
* Error messages. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem.
* Alternative output format. The modular design allows other output formats. XStream ships currently with JSON support and morphing.
Refactoring Java code is far simpler than refactoring a relational database, but fortunately that isn't so much the case with object databases. In this installment of The busy Java developer's guide to db4o, Ted Neward introduces you to yet another advant
Simple Persistence for Java is an open source object-relational persistence library that uses a custom query language and built-in database support to simplify object persistence in Java applications.
JPOX is a free and fully compliant implementation of the JDO1, JDO2 specifications, providing transparent persistence of Java objects. It supports persistence to all of the major RDBMS on the market today, persistence to the DB4O object datastore, supporting all of the main Object-Relational Mapping (ORM) patterns demanded by today's applications, allows querying using either JDOQL, SQL, or JPQL, and comes with its own byte-code enhancer. JPOX is available under the Open Source Apache 2 license, allowing access to not just a top quality Java persistence implementation but also to the source code, allowing you to contribute to the success story of the principal standards-compliant Open Source persistence implementation in the world today.
Common object storage frontend. Common object storage frontend that supports dictionary-style access, object serialization and compression, and multiple storage and caching backends.
OpenXava is a framework to develop easily business applications with XML and Java. Its virtue resides in the fact that the heart of our applications is XML instead of Java. For example, if you want a J2EE application that works with Teachers you only need
Working with Hibernate and attempting to wrap caching services elsewhere in one of our applications, I'm concerned with the way these caching frameworks handle expiration. If you have many different types of domain artifacts that you want to cache with a