Hi,

for a superclass Person, I have two subclasses declared as follows:

/**
*
*
* @hibernate.class
* table="PERSON"
*
* @hibernate.joined-subclass
* table="PLAYER"
*
* @hibernate.joined-subclass-key
* column="PLAYER_ID"
*
* @hibernate.joined-subclass
* table="TEAM_MANAGER"
*
* @hibernate.joined-subclass-key
* column="TEAM_MANAGER_ID"
*/
public class Person implements IPerson, Serializable{
...
}

When I generate the mapping, I get this output:

...
<joined-subclass
name="de.soccermanager.person.entity.Player"
table="PLAYER"
dynamic-update="false"
dynamic-insert="false"
>
<key
column="PLAYER_ID"
/>
...
</joined-subclass>
<joined-subclass
name="de.soccermanager.person.entity.TeamManager"
table="TEAM_MANAGER"
dynamic-update="false"
dynamic-insert="false"
>
<key
column="PLAYER_ID"
/>
...
</joined-subclass>

For both subclasses the generated key-column is set to PLAYER_ID. However, for the class TEAM_MANAGER it should be TEAM_MANAGER_ID. What is wrong?

thx,
sven

I have not found any solution and probably because of a "another" bug in HibernateDocletTask.

I am wondering how many Hibernate users really use this tool and if the "top-down" approach is the best way to go. I mean on a big project with many POJOs it is really a pain if you have to manually correct the generated mappings every time. Furthermore I am forced to check each mapping for the proper convertion, very time consuming and it is easily to oversee wrong entries ...

Maybe one should drop the XDoclet-Hibernate approach at all?! Any experiences?

sven

I use Xdoclet as my preferred approach (current project 200+ tables) most of the others create the mapping xml as their base (work from the middle).

Why not create JIRA issue and ask the XDoclet group..what about XDoclet 2.0 which has better support. What about fixing it and creating the patch - this gives something back. You have many options - some of which help yourself and the community - which is great.

I also prefer XDoclet for setting up my hibernate mappings...


After investigating the xdt mappings of the xdoclet-hibernate module I have to rectify my last statement. I found out, that there is NO bug at all with the joined-subclass attribute. I simply declared the attributes in the wrong class (the superclass instead of the subclasses).

In the past I always used the superclass to declare a subclass. And as long as you have only one subclass to declare it works. That is why I never came up with the idea that the fault is on my side.

Thanks for your little challenge David. Otherwise I had never looked at the source of the hibernate module...

sven

Glad you found the issue and hope you continue with the challenge. Thats how we grow the community and all benefit from it.