is that correct? But the issue is,Įven after successful insertion of five methods in next iteration, the transaction is getting rolled-back. I have used session.clear() method in catch block to avoid that. If, 5th iteration is failed, then in next iteration, old values are showing in the entity.It is OK if transaction is committed after successfully executing all the 5 methods in one iteration. I.,e In 100 iterations if 5th iteration fails and all the other iterations are succeeded, then all the 99 iteration's operations should get committed.
So that DB doesn’t fall in inconsistent mode ever. All these actions in combination will be treated as ONE action only. One iteration fail should not rollback all the other iterations. The sequence of activities that will be performed to complete database operation and its management is known as Transaction Management. I added a sample Aspect to apply Synchronization for annotation driven transaction demarcation. Transaction has to be rolled back even if one method fails in one iteration.(i.e 5 methods has to be saved without exception) and the flow should continue for next iteration. If transaction is in scope, you can get transaction info from TransactionAspectSupportcurrentTransactionStatus(), however I think that spring only call afterCompletion() once. Step 3: Add the Transactional annotation to the insertMember method. To add declarative transaction management to the above method use the following steps: Spring works with the transaction manager to begin and complete transactions. These 5 methods are wrapped under single parent method which is annotated with calling this parent method 100 times in a loop. But it is much easier to let your container handle this. My requirement is to save data in 5 tables through 5 methods.
0 kommentar(er)
