Using @ org.springframework.transaction.annotation.Transactional outside the DAO level?

Question

I have a pretty classic issus: Access Lazy Collection outside of the DAO, because that leads to a LazyInitializationException.

Is this a clean and sensible decision to use @Transactional one of the service methods outside of the DAO that use this lazy collection?

thanks

Answer 1

Yes it is. Anyone who knows what tasks should be a unit of work (transaction) is a service, because it is he who “knows” the business.

Answer 2

Neuquino has the correct answer , but it is not very clear and understandable, so I will try to rephrase it:

Usually you need one transaction for one service method, so you annotate the @Transactional service @Transactional , not the DAO level. (The great thing about Spring @Transactional annotation is that it does not depend on the underlying implementation, so there should usually not be any code at the service level that depends on your persistence level, for example, there are no Session or JPA EntityManager hibernation calls) . For unit testing DAOs, add @Transactional annotations to your test methods (your tests are services, not DAOs).