I'm looking for a way to retain a copy of an object and yet tie it to the original object. The best word I can use is versioning objects so I can see their history. The only way I've thus far figured out how to do this is to create a composite id consiting of an 2 incremented numbers so that when object 101-00 is updated it is actualy copied and saved to 101-01. The documention however warns against using composite keys at all and it seems like there should be a more elegant solution to this. Any ideas?

Still looking for help on this.

We had the same problem:

You must have a logical key (which is unique in recent data) and an actual key in your table.

Then create a view which returns newest valid data, and map both the table and view...

use HQL to find anything you want.