Hi all,
I'm working with Hibrenate 3.2 GA, using annotations to declare Entities and its mappings. I'm having an undesired behavior using an unidirecitonal one-to-many relationship:


entity A has many entities B

where in entity A...

@OneToMany(cascade = CascadeType.ALL)
@JoinTable(name="A_B")
@Sort(type = SortType.NATURAL)
public SortedSet<B> getBs() {
return this.bs;
}

public void addB(B b) {
this.bs.add(b);
}


The resulting behavior is that adding B entities in successive user requests, entities of type B are persisted in its table, but the join table only stores the last inserted relationship between A-B, resulting a one-to-one relationship.

In test, if to B entities are persisted during the same transaction, the result is the desired.

Any clue why this is happening?

thanks in advance,

Marc

mea culpa!

The problem was related to the fact I'm using a SortedSet of entities B, which implement the Comparable interface, where the compareTo only had two cases: bigger or smaller, but I didn't implemented the equals case.

This lead to a strange situation in the org.hibernate.action.CollectionUpdateAction, where it does...

persister.deleteRows( collection, id, session );
persister.updateRows( collection, id, session );
persister.insertRows( collection, id, session );

this deleteRows deleted all the entries from the first transaction, because it compared the existing ones when commiting the transaction with the ones loaded previously, and no one matched because compareTo was allways different!

Thanks for your patience ;-)

Marc