Spring @Transactional Class or annotation method

Question

Trying to collect and understand the main points of the @Transactional annotation and cross one point. So, the main things that we need to keep in mind when using the Transactional annotation are as follows:

• A transactional annotation can only be applied to public methods [according Does the Spring @Transactional attribute work on a private method?
• The transactional annotation should be applied to specific classes instead of interfaces [according to Where should I put the @Transactional annotation: in the interface definition or in the implementation class?
• Transactional annotation should be applied at the Service level [according to Spring @ Best practice of translation annotation
• If you want to exclude any public method from the Transactional annotation when the whole class is annotated, you can use some distribution strategies [according to the transaction annotation for the whole class + excluding one method

Unfortunately, I did not find the answer to the question: where is it better to add the Transactional annotation - to the class or method? We can consider different situations, but basically I'm interested in one thing, when we have several methods that should have this annotation, and some should not.

Plus, maybe you would like to add some points to this list, it would be very cool.

Answer 1

Here is a list of the pros and (implicitly) minuses that I can think of.

Pro:

• . , , , .
• . , . , .
• . , () , ( REQUIRES_NEW ). , , - . , , , , , .

Pro:

• . , . , DRY. , IMHO, DRY, Java private/protected/public .