I'm attempting to convert my application to use hibernate instead of a home-grown half-assed solution.

My app acts as a server to users running a custom client. Each client connection is long-lived has its own thread.

Currently, users can cause the objects on the server to be modified and immediately written to the db. There isn't any synchronization control on this. When writing to the db, transactions are not being used.

Note: my app is the only process that opens the database, and all objects are read into memory during application initialization, and then flushed to db as changes are made.

All users need to see the SAME objects from their connections because these objects represent real physical objects that my application is controling, and that the users are cooperating with each other to manage.

My current main worry is if 2 threads modify a value on the same object (at the same time), will I get data corruption? (ie. obj.setName( newName ) )

I do see in the docs that a Session isn't thread safe, but I'm not sure where all the fancy footwork with hooking setXXX(newval) calls on objects to detect changes stop and Sessions begin.

-Trevor

I guess I should also mention that I'm thinking of using something like the scheme called "Long session with automatic versioning" from the Hib docs.

Basically, it shows it as:



But in my case, I'm hoping that I can modify my foo while the session is still disconnected, and then reconnect and flush: