OK, I can use that to improve th mapping file situation.
But now I have seperate classes, which is a problem, as
A is my persistent base class
B is contained in a collection/set (inverse=true)
the collection/set is once contained in B itself and once in C
now the contained element needs a property and a many-to-one mapping for each possible parent. not nice. I want only one parent of type A, as all are extended from this. But A being abstract is not mapped, only its attributes contained in the mapping of B and C.
What is the solution?
subclass is not, as unpractical in a larger project for ALL classes and I need seperate tables
joined-subclass is not, it does split my tables and is still all in one mapping file.
???
|