Hi all,
I am using hibernate on a client-server application, where client request for server by invoking a command and according to the command, the server calls hibernate to return the data as a response for the client.

The scenario:
client requested x's from server
server gets request, call hibernate session.find(request arguments)
and returns the list of x's.
then the client modify a x object and send another request to server to update the x,
then server throws NonUniqueObjectException a different object with the identifier already associated with the session....

I think hibernate is doing absolutely great work,
, but I wonder how and why why why why it made such a simple update that much complicated??

I know why hibernate throws that exception
there are 2 instances of Class X the same identifier-values.
in the session.

Should I override the equals method to force hibernate to understand that if 2 object have same PK(!!!!!) then they are same objects or what can I do as a better solution?

use saveOrUpdateCopy

but be careful with "saveOrUpdateCopy" ... in HB2 it doesn't work with Collections ...

In 'every' other case it works perfectly for me ...

gtx
curio

I updated Hibernate to 3.0
I used saveOrUpdateCopy of classic session (it is depreciated there?) but it still gives the same error!
In that case why doesnt saveOrUpdateCopy work correctly?

Step 1. Client makes a request to server to send all x'S
Step 2. Server queries and send x's
Step 3. Client unmarshal's response and get x's that server sent (new instances by List xs = (List) unmarshall(response); )
Step 4. I created new y object instance of Y and choose one of the x to make y.setX(x) in client side
Step 5. I send this y to server to save it by session.save()

( in mapping many-to-one name= "x" class = "X" column = "X_ID" )

Hibernate gives me: Save the transient instance before .... exception
I say ok; and I call session.saveOrUpdateCopy(x) before session.save(y).
In my understanding of saveOrUpdateCopy(x) :
Hibernate will look for the x instance with the same identifier value in the session, if founds he calls update, since no changes made to x in the client side, then nothing to be updated rather than the "user" instance loaded instead of the "server" instance with the same identifier . Then save(y) can move on correctly since its x object is in the session anymore. But it can not since hibernate throws now
another exception for saveOrrUpdateCopy(x) : NonUniqueObject exception....

What am I doing wrong? (If there is a simplier way for that scenario I am listening...)

Note: Identifier values of instances are Long
Class X : Long id,...

Can we say that hibernate is not a good choice for a client-server application?

Use the search engine.

http://opensource.atlassian.com/project ... se/HB-1202

my problem is not the saveOrUpdateCopy with cascade throw NonUniqueObjectException.
Did u read the scenario I sent?

Scenario:

I cant still solve the problem...
I need help for the scenario above.

I did.
saveOrUpdateCopy works perfect!
Hibernate works perfect!