Hi,

I got stuck for a while with a java.lang.StackOverflowError exception and I haven't found a solution yet, so I decided to write on forum about it. Maybe someone else run into this problem and manage to solve it.

I have two entities Invoice and Line. Line has a composite PK which contains Invoice PK's. Between Invoice and Line there is a one-to-many relation, with Line the owner side. I have mapped this relation bidirectional as following:

@Entity
@Table(name = "invoice")
public class Invoice implements Serializable
{
...
@Id
@Column(name = "id")
private int id;

@OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER, mappedBy = "id.invoice")
@JoinColumn(name = "id")
private List<Line> lines;
...
}

@Entity
@Table(name = "line")
public class Line implements Serializable
{
...
@EmbeddedId
private LineId id;
...
}

@Embeddable
public class LineId implements Serializable
{
...
@ManyToOne
@JoinColumn(name = "id")
private Invoice invoice;
...
}

Problem is that when I want to get all Line objects based on search criteria (I wrote a dao method that do this task), it gets into a infinite loop causing in the end a java.lang.StackOverflowError exception. I guess that for each Line in search results, for loaded Invoice it belongs to, are also loaded all Line that that Invoice has and so on.

Could someone give me some ideas how can I solve this? Thanks.

I am using hibernate 3.3.2 ga.

How about something like

The cause of the infinite loop might be because to construct a LineId, we need an Invoice but to construct the Invoice we need Lines (eager fetch) which in turn need the LineIds.

I cannot give up in fetching lines eager as I use information from lines objects when I display invoice.

I am wondering if a bidirectional one to many relation will always produce an infinite loop if on both ends fetching mode is set to eager. I guess not, if I am able to set such a relation?!

I think the fact that the related entity is itself the part of the id is what tripped Hibernate I believe. Did you consider the previous mapping I suggested - use of a surrogate key and setting uniqueness constraint on the natural id?