title: Eclipselink - Lazy Load Behavor after Close EntityManager [Best Practice - Better way and how to live]
body: <p>I would like to ask for help on eclipselink (lazy load).</p>
  
  <p>As we all know <strong>Eclipselink</strong>, has a behavior somewhat different from <strong>Hibernate</strong>, <em>unfortunately</em> or <em>fortunately</em> it allows to perform the <strong>lazy load after closing the EntityManager</strong></p>
  
  <p>I've researched a lot on this subject and found nothing in it, is there any way to override this behavior?</p>
  
  <p>Any native paramemter? I noticed that there is anti-pattern for this, but for all the content I read, this would not be the advised way of doing this.</p>
  
  <p>I would very much like a way to bar this behavior.</p>
  
  <p>I tried to use the parameter:</p>
  
  <pre><code>&lt;property name="eclipselink.jdbc.exclusive-connection.is-lazy" value="false" /&gt;
  </code></pre>
  
  <p>But without success.</p>
  
  <p>I tried to find some property, but I was not successful either :
  <a href="http://www.eclipse.org/eclipselink/documentation/2.5/jpa/extensions/toc.htm" rel="nofollow noreferrer">List of Properties of Eclipselink</a></p>
  
  <p>For more experienced developers, how can I improve this behavior within my system? Is there anything I can do about it?</p>
  
  <p>I would like to go a bit more, what benefits we gained from this behavior and what would be a good practice on top of it</p>