Hibernate version:2.0

Hi,

Im having some trouble using xdoclet with hibernate and composite identifiers. I managed to figure out that xdoclet has no support for composite id's with hibernate and one way of 'getting' the id into the hbm.xml file without doing it by hand is to use the merge dir in the ant script. The merge dir would include the xml tags for the composite id into the hbm.xml file. My problem is that the xml file with the extra tags are never included.

My merge dir is specified by eg. mergeDir="C:/xml/merge" for a class: myClass in package: myPackage
And i've put the xml to be merged in the suitable catalogue under this directory (given by the package structure) eg: C:/xml/merge/myPackage/hibernate-properties-myClass.xml

Does anyone see why this should not work? I would be very greatful if anyone have any input in this matter what so ever.

Regards / A. Kikr

Ok, it seems that the xml is merged! But the problem still persists. I added an empty id tag to my java file and now the generation goes through and i can see that the merge has been made but the generation won't go through without the id tag (which is what i want). So it seems the generated xml is checked before additional information is merged into it. Can this really be the case? Any comments anyone?

Does anyone have a workaround for XDoclets lack of support of composite keys for hibernate? I cant think up anything good. Any comments helpful.

Cheers / A. Kikr

Well, considering XDoclet DOES support composite keys I'm not quite sure where you're breaking down.

For our comp keys, we have comp key objects. The class that has the comp key maps the hibernate.id to the comp key object. Then the key object simply has hibernate.property or hibernate.many-to-one tags and it sorts it all out.

Now, if you're having problem with the key many-to-one to an object with a composite id then xdoclet didn't (still doesn't?) handle that. Although my co-worker submitted a patch (to Xdoclet) to provide support for it that we use.

In the end, typically if Xdoclet doesn't do what you need it to do it is sometimes just as easy to modify the xtd(?) files to make it do what you need.

Thanks for the reply Vampboy,

Yes, you are quite right. It seems xdoclet does support composite keys. The thing was i found no information on how to do it or even that it worked, only som post about how it wasn't supported. But indeed i got it to work and it was really the logical way to do it to. I guess I just wasn't thinking straight yesterday :)
If anyone else is struggeling with the same thing here's what to do:

Say you have three classes: Client, Custom and Field. Client has a one-to-many realtionship to Custom, Field also has a one-to-many relationship to Custom and Custom stores a value about the association (M-M) between Client and Field. Cusom should have a composite key of the id of Client and the id of Field. The composite key elements should go in a separate class calles say CustomKey with Custom having a CustomKey instance called say id.
To Customadd:

/**
* @hibernate.id generator-class="CustomKey"
*/

To CustomKey add:

/**
* @hibernate.many-to-one column="field_id" class="myPackage.Field"
*/

/**
* @hibernate.many-to-one column="client_id" class="myPackage.Client"
*/

This worked for me, there's probably a prettier solution or a better one. Thanks for the help though. This forum is awsome!

Cheers / A.kikr

Yep, that is how you do it. Although you don't have to actually specify the class. Xdoclet and Hibernate will figure that all out.

i.e.



Out of curiousity are the key many to ones getting generated properly? Actually I think the actual issue is key many to ones where the one side is made up of a comp key so I think you should be fine for now :)

Yep, that is how you do it. Although you don't have to actually specify the class. Xdoclet and Hibernate will figure that all out.

i.e.



Out of curiousity are the key many to ones getting generated properly? Actually I think the actual issue is key many to ones where the one side is made up of a comp key so I think you should be fine for now :)

I am having the same problem as azzkikr had. Do I need to generate the Setters and Getters in the CustomKey class? Would it be possible for you to provide me a complete example? Sorry I am new to this.

I have this code but it doesn't work:



Please help, what should I do? Thanks.

Newreaders,

I did get your email but I'll respond here instead.

As far as I know this shouldn't end up generating anything....



What you should have is a getter for each of your properties.

In your case if you are simply using Longs to store your properties then it would simply be:

@hibernate.property="roleID"
public Long getRoleID();

@hibernate.property="userID"
public Long getUserID();

Other than that I'm not quite sure what you're trying to do in the Custom class.

Your email stated that you wanted to set up a many-to-many association. If that's just the case and your many doesn't contain any extra info (i.e. it is just a junction table) then you don't actually even need to declare the class.

Thanks