I am having a problem with my already existing objects being persisted into the database when I call saveOrUpdate().
What happens is that I am putting the User object into my servlet session so that I can access the values of the account on the view (JSP pages). When I call on an operation later in the system I may grab that User object out of the session to set the value into a new object that is later persisted with hibernate by calling saveOrUpdate(). This is where the problem occurs... when I save that new object with the User object as a reference it is being repersisted rather than looking at the identy field and seeing that the row/data in the datastore as the same object. Is there a way to force hibernate to look at the existing identify field on the object I am setting rather than resave the existing object over again? Thanks. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
