Hibernate version: 3.1.2
I'm having a serious problem in the mapping of a parent child structure where both parent and child are abstract classes that are derived for differente implementation.
This is the case:
abstract parent and child:
public abstract class Parent {
Long id;
// some properties omitted
List childs = new ArrayList();
// getters/setters omitted
}
public abstract class Child {
Long id;
// some properties omitted
Integer index; // index for ArrayList
Parent parent;
// getters/setters omitted
}
concrete parent and child:
public class Parent1 extends Parent {
// some new properties omitted
// getters/setters for new properties omitted
}
public class Child1 extends Child {
// some new properties omitted
// getters/setters for new properties omitted
}
In the project there are many other classes parent and child that should inherit from Parent and Child; some of these inheriting directly from Parent and Child, other will extends Parent1 and Child1.
For this reason, I would like to centralize the mappings definition at the most possible in Parent.hbm and Child.hbm and extend for other classes.
For the inheritance strategy, I will prefer table-per-concrete-class. Absolutely no table-per-subclass.
My first idea was something like this:
mapping for abstract parent and child:
<hibernate-mapping package="xxx.abstract">
<class name="Parent" abstract="true">
<id name="id" column="id" type="long">
<generator class="sequence">
<param name="sequence">parent_id_seq</param>
</generator>
</id>
<version name="version"/>
<!-- properties omitted -->
<list name="childs" inverse="true">
<key column="parent"/>
<list-index column="index"/>
<one-to-many class="Child"/>
</list>
</class>
</hibernate-mapping>
<hibernate-mapping package="xxx.abstract">
<class name="Child" abstract="true">
<id name="id" column="id" type="long">
<generator class="sequence">
<param name="sequence">child_id_seq</param>
</generator>
</id>
<version name="version"/>
<!-- properties omitted -->
<property name="index" type="integer"/>
<many-to-one
name="parent"
class="Parent"
column="parent"
not-null="true"/>
</class>
</hibernate-mapping>
and for concrete classes:
<hibernate-mapping package="xxx.concrete">
<union-subclass name="Parent1" table="parent1" extends="xxx.abstract.Parent">
<!-- new properties omitted -->
</union-subclass>
</hibernate-mapping>
<hibernate-mapping package="xxx.concrete">
<union-subclass name="Child1" table="child1" extends="xxx.abstract.Child">
<!-- new properties omitted -->
</union-subclass>
</hibernate-mapping>
This mapping is correctly loaded but, at save time, only parent is saved and no errors raised.
I REALLY, REALLY appreciate a suggestion.
Davide
Login
FAQ
Search
