I am in the process of migrating our application to annotations, from hbm.xml mapping.

My goal was to migrate without changing the code, only adding annotations.

My first problem is that our application has a root parent class that is the parent of every hibernate entity.

that class has


private Long id = null;
private Integer version;
protected StatusEnum status = StatusEnum.ACTIVE;
protected String name = null;


Id is mapped to different columns, and uses a different Generator in different entities.

I was going to use the @AttributeOverride, but I was not sure how to do this with the generator.

the other problem is that name and status (and version probably) are not mapped in all of the xml files, so it would just return the default values. This is fine in xml because the values are not referenced in the hbm files

but when I use annotations those fields are caught by reflection.

Is there a recommended way to fix either of these issues?

thanks

Kal

Hi,

given that you are using a class hierarchy I am assuming that all properties make sense in all subclasses (otherwise why use inheritance). So why is it wrong to map the properties for all entities. Just make sure that the objects get initialized with the right default value. Is there a problem to persist the default values?

Regarding the key generation - I guess you could implement your custom IdentifierGenerator which could act as wrapper for your different strategies. Personally I would first try to change my schema so that I for example could use the same generator. Of course that might not be possible.

--Hardy