Hi there,

This is my first post to the Hibernate forums - I'm a big fan of the architecture (I worked on another persistence framework that could have been a kissing cousin of Hibernate).

Here is my inaugural question. I have an application framework that I am integrating Hibernate with. One of the features of this framework is the fact that persistent ID keys are stored in as part of a business objects meta-data (meaning that there is typically not going to be a field on the BO for the persistence key).

As I am building the interface layer between my app framework and Hibernate, I notice that if I retrieve a BO in one session, but attempt to save an update to it in a separate session, it is saved as a new object instance, presumably because the new session has no idea how to get the persistence key from the meta-data.

Anyway, I have RTM'd and I don't see s way right offhand that would allow me to pass the appropriate key to the new session so that it can properly update. Any ideas?

Cheers,

Jonathan House

Hibernate has an overloaded version of update() which takes an id.

Thank you for the quick response. By the way, how was your trip to Wal-Mart?

Regards,

Jonathan House

eh? what are you taking about?

Sorry - should have added more context - I work with MVSC in Utah - I understand they had you come in to do some performance tuning.

Regards,

Jonathan House

OK, well, I guess if I would have been doing any work for large organizations like that recently, it would reflect quite badly on me if people thought I was shooting my mouth off about it without seeking permission from them first...