What approaches can be used to solve problems that occur when calling UserRepository.findById() and User.getEmails().forEach(), if the getUsers() method is annotated with @Transactional and the email field is declared as @OneToMany?

Problems when calling UserRepository.findById() and then accessing User.getEmails().forEach() are often related to lazy loading of collections in JPA/Hibernate and transaction management.

If the method getUsers() is annotated with @Transactional, then the transaction is open at the time of call, and lazy collections are accessible. But if the transaction closes before accessing getEmails(), an LazyInitializationException occurs.

Approaches to solve this:

1. Use @Transactional at the service level so that the transaction remains active during access to lazy collections.
2. Initialize the collection beforehand — for example, with fetch = FetchType.EAGER in @OneToMany, but this can lead to over-fetching.
3. Use JPQL with JOIN FETCH to load the user along with emails:

@Query("SELECT u FROM User u LEFT JOIN FETCH u.emails WHERE u.id = :id")
Optional<User> findByIdWithEmails(@Param("id") Long id);

4. Explicitly initialize the collection within a transaction, e.g., by calling user.getEmails().size().
5. Use DTOs with projections to load only necessary data.

The choice depends on the specific situation and performance requirements.