• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Transcation management at DO level using spring jdbc framework

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
we are using spring jdbc framework in our project.

Right now we have kept the transcation boundry at the service level which the entry point from client side to sever side.
We have applicationContext.xml file where we have defined the transcation boundry condition for each service.

here is piece of code of applicationContext.xml
<tx:advice id="txAdvice" transaction-manager="txManager">
<!-- the transactional semantics... -->
<tx:attributes>
<!--
all methods starting with 'select' or 'get' are read-only
all methods that start with save require a new transaction
-->
<tx:method name="select*" read-only="true" />
<tx:method name="get*" read-only="true"/>
<tx:method name="save*" propagation="REQUIRES_NEW" />
<tx:method name="insert*" read-only="false" propagation="REQUIRES_NEW" />
<tx:method name="update*" propagation="REQUIRES_NEW" />
<tx:method name="import*" propagation="REQUIRES_NEW" />
<!-- other methods use the default transaction settings (see below) -->
<tx:method name="*"/>
</tx:attributes>
</tx:advice>

<!-- @1. Ensure that the above transactional advice runs for any execution
of an operation defined by the service interfaces.
@2. Defines Transaction Manager Boundaries.
-->
<aop:config>
<aop:pointcut id="usersServiceOperation" expression="execution(* com.smartLMS.server.user.services.UserService.*(..))" />
<aop:advisor advice-ref="txAdvice" pointcut-ref="usersServiceOperation" />
</aop:config>

But in one case the entry point is one sevlet from where we call the sevice method and and from service we call a method from domain object
In this case the transcation boundry is not getting applied.
and if i want to set the transaction boundry in DO level how can i do this?

Please help.
 
ranger
Posts: 17346
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
How is the Servlet getting the reference to the service. It must go through the Application Context in order to go through the proxy that sets up transactions. If the Servlet gets the service directly, it won't have a proxy and no transactions.

Mark
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

The servlet is getting refernce to the service from application context only.
The logic of insert is like this
public String saveData()
{
for()
{
try{
insert1();
insert2();
insert3();
}catch(Exception e)
{
// RollBack here
}
}
}

If there is exception in 2nd insert it should roll back the Insert1() also but continue the loop. This logic is present in DO so i need to set the transation boundry condition at DO level.
 
Mark Spritzler
ranger
Posts: 17346
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please post your xxx-servlet.xml configuration and your applicationContext.xml

And please use the CODE tags to make sure they keep their indentation for readability.

Thanks

Mark
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi I am also facing same issue as mentioned by Roopali,

for loop(n)
{
for loop_1()
{
Insert A()
Insert B()
Insert C()
}

for loop_2()
{
Insert D()
Insert E() --> throws RunTimeException
}
}
In above scenario records inserted by Loop 1 should be rolled back. Which is not working.
Flow of code is like

TestService.java(where transaction boundaries maintained) --> DO --> DAOImpl

TransactionAspectSupport.currentTransactionStatus().setRollbackOnly();

Note: I am using spring.jar version 2.0.1
 
prashant shelke
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please see detail post here:

Issue for spring rollback
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic