I had started off my JEE5 experience using TopLink Essentials which for the most part was pretty painless. I noticed a few features that looked to be useful in the Hibernate JPA provider implementation such as @IndexColumn and I must say my painless experience has become very painful.

There has been several things that had broke when I made the switchover but the biggest is the fact that I had two @OneToMany relations which are of FetchType.EAGER. Now this is part of the JEE5 specification from what I understand so why Hibernate does not provide the correct implementation I am unsure.

That being said I am stuck with one being lazy and the accessors for this are based in a Stateless session bean. So now I am constantly getting LazyInitialization errors when this collection is being retrieved.

What is the best way to resolve this instead of being required to change my Stateless bean to Stateful which is something I shouldn't have to do.

Thanks, S.D.

There is a good article describing exactly why you encounter this problem and several potential solutions one of which I tried and it works great!

http://www.jroller.com/eyallupu/entry/hibernate_exception_simultaneously_fetch_multiple