Hi,

I'm using hibernate 2.1, and while I have used xdoclet for other things, this is the first time with hibernate. It seems that my generated mapping file is not generating the ID correctly. Here's the POJO:

/**
* @hibernate.class table = "CAT"
*/
public class Cat {

private String id = "";
private String name = "";
private String sex = "";
private float weight = 0.0f;

public Cat() {
}

/**
* @hibernate.id generator-class = "uuid.hex" column = "CAT_ID"
*/
public String getId() {
return id;
}
...

Here's what it generates:

<hibernate-mapping>
<class name="entities.Cat" table="CAT">
<id name="id" column="CAT_ID" type="java.lang.String">
<generator class="uuid.hex"></generator>
</id>
<property name="name" type="java.lang.String" column="name" />
<property name="sex" type="java.lang.String" column="sex" />
<property name="sex" type="void" column="sex" />
<property name="weight" type="float" column="weight" />
</class>
</hibernate-mapping>


But hibernate doesn't like that (net.sf.hibernate.MappingException: Error reading resource: entities/Cat.hbm.xml). Here's the hand-coded mapping file that works:

<hibernate-mapping>
<class name="entities.Cat" table="CAT">
<id name="id" type="string" unsaved-value="null">
<column name="CAT_ID" sql-type="char(32)" not-null="true" />
<generator class="uuid.hex" />
</id>
...
</class>
</hibernate-mapping>

So, my question is, how do I get that mapping from xdoclet? Or is there something else fundamentally wrong?

Thanks,

Don

You just have to form your XDoclet markup to produce the mapping you want. You hand crafted example has a separate column tag so you need a separate XDoclet markup line, eg, something like

I tried that, and I get the following, which is even worse...

I just played around with it (not lastest version of XDoclet though) and it appears it ignores the column tag when used with the id tag. It works correctly with the property tag. This limitation should be sent to XDoclet's JIRA so it can be fixed. For now you should get a working mapping by simply using.

Sorry to be a pain, but the above code doesn't work. That was my first stab at it, and trying it again gives me the same mapping file that hibernate is just as unhappy with. I know that I can hand-build the correct XML, but that doesn't help my team as we are building our application. I'll try sending a JIRA to the XDoc team. Looks like it's hand-building in the mean time.

Don

What is the error - it should be OK. I quickly re-read the thread and I cannot see any major difference between your orginal XDoclet mapping and the hand coded one (other than the unsaved-value). You should try and see what is wrong with it - not the generator open and close tags with no contents? I cannot try it out at the moment but maybe later.

Turns out it was the DTD referring to the hibernate-mapping-1.1.dtd instead of 2.0. Changing that fixes it, but I'm wondering how to fix the xdoc generator, which I run from Eclipse.

Xdoclet script is fairly easy to understand. Have a look at the source. You could also create JIRA entries for the request(s) that you have.