Is there a reason there is no get(obj, id) method in the Session API, although there is load(...) like this.

The thing is, I made some wrapping API around hibernate and I need the same semantics for load() and get().

Any suggestions (I need a load by object behavior for get())

thanks.

Michael.

load() assumes the row exists in the DB, and so can fill the object you pass to it with the data loaded and throw an exception when the row is not found. What should get() do when the row is not found?

I guess get(_obj, id) should do the same as get(Class, id) does, but instead of returning the Object that found in session it should fill the given _obj with the proper content.
it just cleaner to have the same semantics for load and get, unless it is fundamentally different?

Michael.

But what if there is no row in the database for the id? get normally returns null in this case, but it really cant if you pass it an object.

If you have a wrapper anyway, well if you want the same behaviour just delegate your call to load()

but this is exactly my problem:

wrapper read(...) gets object ref to some POJO then it tries to load() but sometimes it is done in the same session and I get "identical objects exception" from load, I thought I could call get and if it fails call load. This way I isolate the user from knowing if he runs in the same or different sessions.

Now back since I have a ref to the POJO using existing API I can not do it transparently?