Where should I put @Transactional annotation: at an interface definition or at an implementing class?

by

From http://static.springsource.org/spring/docs/2.0.x/reference/transaction.html

The Spring team’s recommendation is that you only annotate concrete classes with the @Transactional annotation, as opposed to annotating interfaces. You certainly can place the @Transactional annotation on an interface (or an interface method), but this will only work as you would expect it to if you are using interface-based proxies. The fact that annotations are not inherited means that if you are using class-based proxies then the transaction settings will not be recognised by the class-based proxying infrastructure and the object will not be wrapped in a transactional proxy (which would be decidedly bad). So please do take the Spring team’s advice and only annotate concrete classes (and the methods of concrete classes) with the @Transactional annotation.

Note: Since this mechanism is based on proxies, only ‘external’ method calls coming in through the proxy will be intercepted. This means that ‘self-invocation’, i.e. a method within the target object calling some other method of the target object, won’t lead to an actual transaction at runtime even if the invoked method is marked with @Transactional!

(Emphasis added to the first sentence, other emphasis from the original.)

More Related Contents:

  1. What’s the difference between @Component, @Repository & @Service annotations in Spring?
  2. Difference between and
  3. Where does the @Transactional annotation belong?
  4. Does Spring @Transactional attribute work on a private method?
  5. Spring: @Component versus @Bean
  6. Only using @JsonIgnore during serialization, but not deserialization
  7. @RequestBody and @ResponseBody annotations in Spring
  8. Xml configuration versus Annotation based configuration [closed]
  9. @Resource vs @Autowired
  10. How to inject a Map using the @Value Spring Annotation?
  11. JsonMappingException: No suitable constructor found for type [simple type, class ]: can not instantiate from JSON object
  12. How to configure MappingJacksonHttpMessageConverter while using spring annotation-based configuration?
  13. @Transactional(propagation=Propagation.REQUIRED)
  14. Annotations from javax.validation.constraints not working
  15. How can I reload properties file in Spring 4 using annotations?
  16. How to scan multiple paths using the @ComponentScan annotation?
  17. How to parameterize @Scheduled(fixedDelay) with Spring 3.0 expression language?
  18. Spring: define @RequestMapping value in a properties file
  19. intellij incorrectly saying no beans of type found for autowired repository
  20. Spring @ContextConfiguration how to put the right location for the xml
  21. Spring annotation-based DI vs xml configuration?
  22. Spring MVC: difference between and tags? [duplicate]
  23. What are annotations and how do they actually work for frameworks like Spring?
  24. Dynamic spring data jpa repository query with arbitrary AND clauses
  25. No serializer found for class org.hibernate.proxy.pojo.bytebuddy.ByteBuddyInterceptor
  26. What is the ‘best’ way to do distributed transactions across multiple databases using Spring and Hibernate
  27. Maven BOM [Bill Of Materials] Dependency
  28. Handle error 404 with Spring controller
  29. Class Conflict when starting up Java project: ClassMetadataReadingVisitor has interface org.springframework.asm.ClassVisitor as super class
  30. Mapping JPA or Hibernate projection query to DTO (Data Transfer Object)

Leave a Comment