Hi, "party" is a detached object that I subsequently attach. I was
expecting to see some "update sql" when I call the session.update.
There's none !!

Thanks

Session session = PersistenceManager.getSession();

party = new IndividualParty();
party.setUserName("testuser");
party.setPassword("testuserpassword");

IndividualPartyHibernateDAO dao = new IndividualPartyHibernateDAO();
party = dao.find(party);
party.setUserName("changedtestuser");
party.setPassword("changeduserpassword");
session.evict(party);

IndividualParty dsParty = dao.find(party);
session.evict(dsParty);

session.lock(party, LockMode.NONE);

party = dao.update(party);

PersistenceManager.closeSession();

Well, the "party" is already associated with the session (since you locked it). So at that point, Session.update() is no-op.

Session.flush() is what forces Hibernate to execute sql statements to the DB. I do not see flush() in your code.

This is all covered in the docs.

Thanks for the response Steve.

Actually, the dao.update() is implemented as

session.update(object);
session.flush();

I also ensured that the flush is in fact being called.

V

In general, its probably best if you leave "DAO" code out of these posts. You may know what they do, but I assure you we have no clue.

I don't even know where to start. In the middle of this "test" you load some "dsParty" and then promptly do nothing with it. Why? At the very beginning you instantiate a "party" and set some attributes, but then immediately throw that instance away when you do the find. Why?

What is it you are trying to test? Then lets write a test that tests that, and then we can see where your code is broken.

If you are simply trying to test updating of detached objects, then try this: