What's the correct fix for a LazyInitializationException, and what's the common wrong fix?

The correct fix is either initializing the needed association before the persistence context closes (JOIN FETCH/Entity Graph for that specific access pattern) or restructuring code to access it while the session is still open. The common wrong fix is making the association globally EAGER, which resolves the one call site's symptom while silently loading that association everywhere else the entity is used, often introducing a new over-fetching or N+1 problem.