Does Spring Transactional attribute work on a private method

Question

If I have a  Transactional -annotation on a private method in a Spring bean  does the annotation have any effect   If the  Transactional annotation is on a public method  it works and open a transaction   public class Bean     public void doStuff          doPrivateStuff           Transactional   private void doPrivateStuff                  Bean bean    Bean appContext getBean  bean    bean doStuff

User · Answer

The answer your question is no -  Transactional will have no effect if used to annotate private methods  The proxy generator will ignore them   This is documented in Spring Manual chapter 10 5 6      Method visibility and  Transactional      When using proxies  you should apply   the  Transactional annotation only   to methods with public visibility  If   you do annotate protected  private or   package-visible methods with the    Transactional annotation  no error   is raised  but the annotated method   does not exhibit the configured   transactional settings  Consider the   use of AspectJ  see below  if you need   to annotate non-public methods

User · Answer

Yes  it is possible to use  Transactional on private methods  but as others have mentioned this won t work out of the box  You need to use AspectJ  It took me some time to figure out how to get it working  I will share my results   I chose to use compile-time weaving instead of load-time weaving because I think it s an overall better option  Also  I m using Java 8 so you may need to adjust some parameters   First  add the dependency for aspectjrt    lt dependency gt       lt groupId gt org aspectj lt  groupId gt       lt artifactId gt aspectjrt lt  artifactId gt       lt version gt 1 8 8 lt  version gt   lt  dependency gt    Then add the AspectJ plugin to do the actual bytecode weaving in Maven  this may not be a minimal example     lt plugin gt       lt groupId gt org codehaus mojo lt  groupId gt       lt artifactId gt aspectj-maven-plugin lt  artifactId gt       lt version gt 1 8 lt  version gt       lt configuration gt           lt complianceLevel gt 1 8 lt  complianceLevel gt           lt source gt 1 8 lt  source gt           lt target gt 1 8 lt  target gt           lt aspectLibraries gt               lt aspectLibrary gt                   lt groupId gt org springframework lt  groupId gt                   lt artifactId gt spring-aspects lt  artifactId gt               lt  aspectLibrary gt           lt  aspectLibraries gt       lt  configuration gt       lt executions gt           lt execution gt               lt goals gt                   lt goal gt compile lt  goal gt               lt  goals gt           lt  execution gt       lt  executions gt   lt  plugin gt    Finally add this to your config class   EnableTransactionManagement mode   AdviceMode ASPECTJ    Now you should be able to use  Transactional on private methods   One caveat to this approach  You will need to configure your IDE to be aware of AspectJ otherwise if you run the app via Eclipse for example it may not work  Make sure you test against a direct Maven build as a sanity check

User · Answer

The Question is not private or public  the question is  How is it invoked and which AOP implementation you use  If you use  default  Spring Proxy AOP  then all AOP functionality provided by Spring  like  Transactional  will only be taken into account if the call goes through the proxy  -- This is normally the case if the annotated method is invoked from another bean  This has two implications   Because private methods must not be invoked from another bean  the exception is reflection   their  Transactional Annotation is not taken into account  If the method is public  but it is invoked from the same bean  it will not be taken into account either  this statement is only correct if  default  Spring Proxy AOP is used     See Spring Reference  Chapter 9 6 9 6 Proxying mechanisms IMHO you should use the aspectJ mode  instead of the Spring Proxies  that will overcome the problem  And the AspectJ Transactional Aspects are woven even into private methods  checked for Spring 3 0

User · Answer

Same way as  loonis suggested to use TransactionTemplate one may use this helper component  Kotlin     Component class TransactionalUtils                  Execute any  block  of code  even private methods         as if it was effectively  Transactional               Transactional     fun  lt R gt  executeAsTransactional block     - gt  R   R           return block             Usage    Service class SomeService private val transactionalUtils  TransactionalUtils         fun foo             transactionalUtils executeAsTransactional   transactionalFoo                private fun transactionalFoo             println  This method is executed within transaction             Don t know whether TransactionTemplate reuse existing transaction or not but this code definitely do

User · Answer

By default the  Transactional attribute works only when calling an annotated method on a reference obtained from applicationContext  public class Bean     public void doStuff         doTransactionStuff           Transactional   public void doTransactionStuff             This will open a transaction  Bean bean    Bean appContext getBean  quot bean quot    bean doTransactionStuff     This will not  Bean bean    Bean appContext getBean  quot bean quot    bean doStuff     Spring Reference  Using  Transactional  Note  In proxy mode  which is the default   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  Consider the use of AspectJ mode  see below  if you expect self-invocations to be wrapped with transactions as well  In this case  there won t be a proxy in the first place  instead  the target class will be  weaved   i e  its byte code will be modified  in order to turn  Transactional into runtime behavior on any kind of method

User · Answer

Spring Docs explain that       In proxy mode  which is the default   only external method calls   coming in through the proxy are intercepted  This means that   self-invocation  in effect  a method within the target object calling   another method of the target object  will not lead to an actual   transaction at runtime even if the invoked method is marked with    Transactional       Consider the use of AspectJ mode  see mode attribute in table below    if you expect self-invocations to be wrapped with transactions as   well  In this case  there will not be a proxy in the first place    instead  the target class will be weaved  that is  its byte code will   be modified  in order to turn  Transactional into runtime behavior on   any kind of method    Another way is user BeanSelfAware

User · Answer

If you need to wrap a private method inside a transaction and don t want to use aspectj  you can use TransactionTemplate    Service public class MyService         Autowired     private TransactionTemplate transactionTemplate       private void process            transactionTemplate execute new TransactionCallbackWithoutResult                  Override             protected void doInTransactionWithoutResult TransactionStatus status                    processInTransaction                                          private void processInTransaction

User · Answer

The answer is no  Please see Spring Reference  Using  Transactional        The  Transactional annotation may be placed before an interface definition  a method on an interface  a class definition  or a public method on a class

[java] Does Spring @Transactional attribute work on a private method?

Examples related to java

Examples related to spring

Examples related to transactions

Examples related to annotations