Hi,
I would not recommend usage of FetchType.EAGER in a many-to-many relationship,
because on loading one parent, it might happen that half of the database is
loaded, if fetching cascades from parent to childs to other parents to other
childs and so on ;-).
Better use LAZY and provide some meth
Wow, I almost forgot about this.
I still do not know what the problem is with this implementation of
@ManyToMany. Actually, I do not believe anything is wrong with the code as
written. I am fairly certain there is a problem with Hibernate, the entity
manager, data marshaller, or something els
Will someone from JBoss look at this? Unless I have made a misstep this is a
significant problem. I have only seen this with eager fetching. Maybe this is
a problem with the entity manager or maybe it's a problem with the data
marshaller. I am not sure what it is, but something is cutting of
