Hi,

I am using the latest nightly build from hibernate tools in order to get a correct naming of foreign-key properties.

Problem is that the generated properties are named in a not predictable manner as i want to do them.

There are 4 foreign keys in my table, if i put in one <foreign-key> fragment, the resulting property of the foreign key is generated correctly.

If I specify all four elements, one naming is always broken. I code them always in the same manner:



In this case I want to have the resulting property named "auction".

Do I make something wrong with the "constraint-name" attribute?
How do I have to handle it? Filling in the FK constraint here produces errors.
Other strings dont seem to affect anything, what is it for?

Thx for help,

cheers,

Gerald

in naming many-to-one and set the only thing that is used at the moment is the constraint-name.

This means that when the jdbcbinder processes the foreignkeys it asks the reverseengineering strategy what name it should use for this foreign key - and here the lookup is purely done on the constraint-name.

The issue then becomes that if you are *also* specifying foreign-table etc. you are actually (as it is now in the current release) ADDING a foreignkey constraint into the model that the jdbcbinder processes - and this end up resulting in a "wonderfull" mix of things.

Thus I would love if you could try doing your naming *without* foreign-table/column-ref and basically just use constraint-name and let me know if that works as you want it....and if it doesn't please submit a testcase to jira for me too look at.

Ok..thx for helping out on this issue.

This works now if only specifying:



The editor marks the corresponding xml as an error, but that doesn`t matter.

cheers,

Gerald

it is just because the bundled dtd in the plugin is outofdate - will be fixed