Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.0

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

I have a unidirectional association between address and user. Association is from user to address. I query user and address in different sessions. That's why the address object that is in the user object and the address object i query alone is different.(they are not refer to the same memory location). how can i handle this problem?

dont use different sessions if you want identity.

i know that for object identity i must use the same session,
but for my application it is not possible.

is there any other nice way of doing this by hibernate.

thnx...

What are you trying to accomplish by having the different queries return the same address object?

actually in my project i have different objects (not address and user) but to make things simpler i gave user and adress example.

in the gui there is something like list all the addresses.
i get these adresses from the database. when a change made on this address object it is not reflected to the user object, because the address object that user has is different from the address object that we make changes.
so i want only one object.

do not say donot take addresses from database, take them from the user objects. there are some addresses that donot have a user. so i cant do that.

if you cant use the same session or associate all the related objects back to one session you cannot get object identity.

ok i get it :)
thnx

You may need to use events or another mechanism to re-retrieve relevant addresses after the user is submitted.

Simplest is to have the user-change process directly update the address view

submitUser(User u) {
persistence.save(u);
AddressView.getCurrent().updateAllAddresses();
}

but the coupling in that sucks, so use the event pattern where you send to an event manager either the specific item that changed or a generic constant indicating the type of object that changed. The address part of the application can listen to that and update it's data.

Use a "coarse-grained" event (like all addresses changed) if you can get away with it. If updating all addresses is slow and/or happens very often, you can pass the changed user or address's ID around in the event so the view can be smarter about updating.