max wrote:
hmm...I *think* this is because you are actually double defining the foreign key...and currently I don't detect this.
You should be able to workaround this by simply only refer to the foreignkey by constraint-name.
Code:
<foreign-key constraint-name="PK_TBENUTZER_STATUS" >
<many-to-one property="benutzerStatus"/>
</foreign-key>
I would appreciate if you put this issue into jira so i remember to either error or handle the case.
hmm this is not working either. If i try it with the workaround above, the property names are wrong again:
Code:
private BenutzerStatus tbenutzerStatus;
instead of
Code:
private BenutzerStatus benutzerStatus;
But at least there is only one tzugang property (i0m still wondering where i can define this name):
Code:
private Set tzugangs = new HashSet(0);
btw: the foreign-key attribute complains about a missing foreign-table argument!
Angela