Hi,
I am new to using Hibernate(v3.2.0) and try to find a fix for this mapping problem:

-Assuming a class Person with *only* a SSN field in it, along with a Person table with columns ID and SSN. ID column is the primary key, and SSN column is also unique.
-Assuming the class and table can NOT be changed, is there a way to create a mapping that inexplicitly populate the ID column in the Person table in this operation:

Person p = new Person();
p.setSSN('123-45-9999');
session.save(p)

Also when the object is fetched, the ID column is automatically ignored.

Your help is greatly appreciated!

-Herbert

Why don't you want to have an ID field in your Person table. The accessors for this field can be protected if you don't want it to be accessible from outside the class

I assume you mean an ID field in Person class. In my application, the Person class is a Legacy class and under different contexts it was mapped to different tables in different data bases where SSN is enough.
-Herbert

But if the ID attribute has protected setters, it would be invisible from outside the class.
In context where it is not required, it would not be assigned : where is the problem ?
I think JDO takes care of this kind of transparent ID but it has other drawbacks

If there is no way to avoid addding the ID field, I will add it then. Even though I prefer not to do it to keep the class as "clean" as possible.
-Herbert