Hello,

We are implementing thick clients using swings. For binding data objects with data objects, at client side, we are using some kind of binding mechanism so that changes can be synchronized on both sides, ie as soon as user make any change or vice versa. So as per our requirement, we have to pass data objects from the server to the client side and vice versa for persisting states to database.

I need help for this scenario, that how can we achieve it. Ok, we can pass the data object to the client after getting it from database and then can work on it. But after getting that object back to the server,

1. How will we synchronize it with the existing system?

2. Do we need to implement Interceptor.isUnsaved method to indicate that this object is a new one or just for updation?

3. And whats about concurrency management, as if two clients demand the same data object at the same time and make changes, then how this will be managed while saving object? "Point is that we got both data objects from the client after deserialization".

Waiting for help..

Thanks!

There is a writting mistake in second line, this should be:

For binding data objects with UI, at client side, we are using some kind of binding mechanism so that changes can be synchronized on both sides, ie as soon as user make any change or vice versa.

1. reatattch the object with session.lock(object, LockMode.NONE).

2. No, unsaved-value is enough if you use non-composite ids or a version/timestamp property

3. Use optimistic locking with a version/timestamp column.

I will take care not to crosspost the topics, that was just mistake.

And Thanks for the solution. I will try with recommended approaches.