I believe there's a bug in the joinedSubClass xml generation using attributes. if you inherit from a class, and use JoinedSubClass attribute,
you end up having another table with all inherited properties again.
also if you have collections on your parent class, you will probably get the Shared References exception from hibernate.

Using attributes is pretty comfortable, but this is a real problem. (unless i'm doing something wrong...)

This is a know issue... We are working on it and a new implementation will be available soon :)

Thanks for your quick reply.

I rarely post issues on forums, i always look (and ussualy find) the answer at google. actually after your reply i searched for "JoinedSubClass" at the Issue Navigator and didn't find any results.

I've posted another issue at the Development forum related to serialization of PersistentCollection class, i had to recompile the nhibernate code to resolve that one.

Anyway, I hope i'm not posting known issues, maybe i'm not looking in the right place? Anyway, thanks again.