Hi,

(I know this has been discussed extensively, but I still have a question.)

Suppose I have an entity bean with a property (a collection) that is is annotated as being fetched lazily. I load the main entity bean with
EntityManager.find() outside any transaction (that's fine), but the moment I wish to access the lazy property I get the lazy initialization exception.

What is the reasoning behind such behavior? I've read about possible inconsistencies between the main entity and the properties, but why is it different from lazy loading the property in a transaction?

To workaround the problem I've implemented a utility bean that loads the entity and iterates over all its properties in a short-lived transaction and then returns the fully initialized entity to the caller. Is there a problem with such workaround? Or is it better to load the property's collection with EntityManager.createQuert().getResultList() ?

Thanks in advance!

For the sake of future references:
I've found a better workaround that uses the fetch hint as in



That should prevent any LazyInitializationException s