no because it would be a really really bad idea to not lazy
So how should I implement my persistence unit tests with lazy loading enabled?
I´m unit testing my DAOs and my test methods are not in a session bean, so when I access my entities (the ones returned from the data base), the transaction is closed and LazyLoadingException is thrown.
1. simulate the transaction boudaries / session lifecycle in your test boudaries
2. use JBoss Embeddable eJB3 in your unit test