Yeah this is a gret feature I do use with Hibernate 3 a lot from the
time I discovered it ... I really do recomend it to all of the Hibernate
users for large entitie like a person esp. for those running on a
multi-tier architecture. I use a base Person object for listings and an
PersonExt for detailed views. However still haven't tried it in the
following situ: I have a UniPerson object as an attribute of the User
class, this UniPerson is actually only an interface and the
implementations are Student etc, Student of couse is the light version
the table consists of attributes of my StudentExt class .. so I wonder
what happen if map it .. I hope and assume that when Hibernate loads my
UniPerson object for the User class it woudle be actually allways the
light version of the implementign class. I will test that soon and come
back ...