Thank's for your answer.
I don't know if it was a bug in older version .. but as you were using the "abstract" attribute of bean element, I noticed that i was using spring 1.0.2 and not spring...
Type: Posts; User: beryOli; Keyword(s):
Thank's for your answer.
I don't know if it was a bug in older version .. but as you were using the "abstract" attribute of bean element, I noticed that i was using spring 1.0.2 and not spring...
Thanks for your demonstration, I'll try that as soon as possible and will surely tell you what it did for me .. as far as i see it, the only thing different is inside the spring configuration file .....
as I see it, it has more to do with the way spring manages the transactions .. the only change i have to do to make it work is adding
Transaction tx = session.beginTransaction()
and
...
I don't think we use the same session object, as Session objects are ThreadLocal objects (so .. if i understand clearly, it's local to the current Thread...)
that's why i don't understand ..
Still no idea ? I've send a mail directly to Juergen Hoeller but haven't received any answer yet ..
It is really urgent,
Thank you in advance,
Oliver
and i believe that my problem is with the way i do it with Spring, because working with Hibernate directly, works ..
public int incrementQuestionCounter() {
try {
Session session...
So i got a main class TestQuestionCounterDao
package **.****.***.main;
import org.springframework.context.ApplicationContext;
import **.****.***.dao.ApplicationContextFactory;
import...
Hi,
I'm trying to apply pessimistic locking on a field in one of my DB tables, using PostgreSQL, Spring and Hibernate.
I tested my locking with two threads trying to read the field (select .....