My classes:
class A {
long id;
String abc;
}

class B extends A {
}

My mapping:
<hibernate-mapping>
<class name="A" table="A">
<!-- automatically incremental log ID -->
<id name="id" type="long" access="field">
<column name="ID" not-null="true"/>
<generator class="native"/>
</id>

<!-- basic properties -->
<property name="abc" type="string" not-null="false"/>
</class>
</hibernate-mapping>

Is it possible when I in my DAO when I call

getHibernateTemplate().save(new B());

it'll still use A's mapping instead of complaining that B is not mapped?

Regards,

What's the point of having B then?


Farzad-

B can have other values but I don't want to store those. ie
class B extends A {
String value;
String value2;
}

I believe there is an overloading save method that accepts entity name and object. You could use that, but in general this is a poor design.



Farzad-

Another aproach would be to properly Map the subclasses of A using the single_table strategy.

It would have the benifit, that you'll get Bs out of Hibernate when selecting objects.