Background: I am using Hibernate 3 in a web application. I use OpenSessionInView filter to open a session-per-request. On each request I start hibernate transaction and at the end I make: commit transaction. If any exception occurs I make a rollback.

Problem:
I have a screen that shows an object and its childs are detailed in a table. One column in the table is editable and the user can change a specific value of the childs. The screen has sevral commands. Some of them causes the screen to be relaoded. meaning that a session will be recreated on each request of the reload.

My problem is, that when I change some values of the childs and just press a link that causes the page to be reloaded, the data is somehow being saved to database by Hibernate. I also have a link in which I directly save the specific object, but it seems that the child objects are saved anyway, only be reloading the page by pressing some other link.

Does Hibernate saves child data even without directly specifying session.saveOrUpdate() ? I have a lot of other screens in my application that never did this problems ...

Hi,

I have the same problem. The thing is that if you enable cascade mode (save-update, for example), Hibernate runs 'cascade checker' code when your transaction commits (flushes all changes to objects), and this is when your updates are performed.
Now the question is: how do you tell Hibernate to use cascade actions only when you do update or save? Unfortunately I haven't found the answer yet. Maybe someone will read this and help us both.

HTH,

Bratek

I believe you can set AutoFlush on the session to be never. The exact semantics would be something to the effect of:

session.setFlushMode(FlushMode.NEVER);

Obviously, this has some other side-effects I'm not really an expert at Hibernate so use your judgement.

Hope this helps
Derek

Thanks!