Question

I have a Spring+Hibernate application with declarative transaction management.
I have a service (FooService) which has 2 public methods MethodA and MethodB. The client will call the MethodA which in turn will call the MethodB.

Client -> MethodA -> MethodB

I want the transaction to start only from MethodB onwards.
This is a snippet from my spring application-context:

<bean id="FooService"
    class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean">
    <property name="transactionManager" ref="transactionManager" />
    <property name="target" ref="FooServiceTarget" />
    <property name="transactionAttributes">
      <props>
        <prop key="MethodB">PROPAGATION_REQUIRED,-FooException</prop>
      </props>
   </property>
</bean>

However, when I invoke the MethodA from my client, it doesn’t create a transaction proxy when MethodB is to be called.
If I add MethodA also to the bean configuration in application-context, the transaction proxy is invoked (starting MethodA, as expected).
Why is this so? Can I achieve transaction being created only from MethodB onwards?

Answer 1

Client -> MethodA -> MethodB

I want the transaction to start only from MethodB onwards

This can’t work. Method A and Method B are inside the same proxy.

The only proper thing to do is to move method B into a different Bean.

BTW: this has been asked many times before, here are some previous answers of mine:

• Understanding Spring transactions – What happens when a transactional method calls another transactional method?
• Spring @Transactional method – participating transaction
• One Service method invoke inner multiple method for Spring transaction