I have a class Person which has a relation to PhoneNumber. The latter has to be a component. Person has two methods for the relation:




PhoneNumber contains String attribute phoneNumberNational and country attribute, which is a Business Object.

I cannot beat the mapping problem with this:

I posted a bug report to the xdoclet jira last spring about this. The answer I got from Gavin was IIRC, given the architecture of xdoclet, the problem is not fixable.

I ended up mapping the component separately and using a one-to-one association between them. It works, although there is almost certainly a performance loss, but at least in my case it's too small to notice.

Can you please show me a code example of your solution?

Forget about it. Now I know what you mean.

I think I need your source code example. It does not work.

Sorry, I meant to say many-to-one association. one-to-one is somewhat useless, while many-to-one is what you want when you want something whose semantics are similar to normal java references. Anyway, in your example it would be:

/**
* @hibernate.many-to-one
* class="com.foo.PhoneNumber"
* column="businessphonenumber_id"
* cascade="all"
*/
public PhoneNumber getBusinessPhoneNumber() {
return businessPhoneNumber;
}

And a similar thing for the private number (remember to use another column name for that!).

You also have to map the PhoneNumber class to the database.

Now it works, thank you. Normally its a one-to-one relation and not a many-to-one relation. But as you said, one-to-one causes problems.

Maybe XDoclet 2 will have no problems with making component relations.