I am facing some problem in transaction commit/rollback.

The situation is I want to update the record before deleting it. So if either of update or delete fails the current transaction should be rolled back, else it should be commited.
In my DAO Impl class delete method I have written following code.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
getHibernateTemplate().getSessionFactory().getCurrentSession().getTransaction().begin();
// update Record
getHibernateTemplate().update(DTOObject);
// delete Record
getHibernateTemplate().delete(DTOObject);
getHibernateTemplate().getSessionFactory().getCurrentSession().getTransaction().commit();
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

But after I call commit on transaction in only calls delete query on database. Not the update one.

I tried with declarative transaction management also, by configuring Transaction attributes in config files as follows:-

<bean id="dataSource"
class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="${jdbc.driverClassName}" />
<property name="url" value="${jdbc.url}" />
<property name="username" value="${jdbc.username}" />
<property name="password" value="${jdbc.password}" />
</bean>
<bean id="sessionFactory"
class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
<property name="dataSource" ref="dataSource" />
<property name="configLocations">
<list>
<value>classpath*:hibernate.cfg.xml</value>
</list>
</property>
</bean>

<bean id="txManager"
class="org.springframework.orm.hibernate3.HibernateTransactionManager">
<property name="sessionFactory" ref="sessionFactory" />
<property name="dataSource" ref="dataSource" />
</bean>

<tx:advice id="txAdvice" transaction-manager="txManager">
<tx:attributes>
<tx:method name="get*" read-only="true" />
<tx:method name="*" rollback-for="org.hibernate.exception.ConstraintViolationException" />
</tx:attributes>
</tx:advice>

<aop:config>
<aop:pointcut id="fooServiceOperation"
expression="execution(* x.y.classname.*(..))" />
<aop:advisor advice-ref="txAdvice" pointcut-ref="fooServiceOperation" />
</aop:config>

And for declarative transaction management, in my DAO Impl class I am writing update & delete in single method as :-
+++++++++++++++++++++++++++++++++++++++++++
getHibernateTemplate().update(DTOObject);
getHibernateTemplate().delete(DTOObject);
++++++++++++++++++++++++++++++++++++++++++++

But Still its only calling delete query on database, not the update one.

Could you please let me know how can I achieve this - it should call both queries on DB or it should call neither.

Many thanks in advance.

-Pras

With a explicite flush() between update and delete you force hibernate to do the update.
(I assume that without flush hibernate swallows the update action as the entity will be deleted anyway)

Hi,

If you are using spring to manage the transaction, don't call begin or commit transaction manually.
What's your purpose of calling update before deleting the entity?
Try to call

before calling delete

So if I call session.flush() it will force hibernate to call update query before delete.

But what about rollback? If delete fails then will it rollback update also?

Also my purpose for calling update before delete is, it is required for audit purposes so I am updating field needed in audit for last update/delete operation.

YES, the rollback rollbacks the whole actions you made since beginning the transaction (beginTransaction)