In Martin Fowler's Pattern of Enterprise Application Architecture, there are several patterns that really
work with Toplink.
Data Mapper: a series of classes that can accept a Java domain object and populate it with
database table/column data using a simple DBField=JavaObjectAttribute equation. The problem is (as we see later...) that
the equation is a little more complex.
The Identity map: a layer that stores objects in a Java Map. In a mapping there is typically one Map per Class, but there
are several types of Maps available with Toplink. The Identity map utilizes primary key information to retrieve the object.
The Unit of Work: a layer that understand the relation between the Identity Map and the database. It knows when to update,
when to clear the cache. A typical implementation is build around JDBC commit() calls.
