Hi Brent, a couple of ideas...
On Aug 6, 2004, at 3:38 PM, Brent Johnson wrote:
<snip...>
Here's an example.. the user logs in and I put the bean in the session. It has a User.name property set to "johnson". Lets then say later during the web transaction I make a SOAP call that does a hibernateSession.load(User.class, pkid) then changes the username to "brent" via Hibernate with myUser.setName("brent"), then hibernateSession.save(myUser).
All fine.. but when the user clicks a button and I read the bean using cocoon.session.getAttribute("user") it still retains the old bean values and the User.name value is still set to "johnson".
This sounds like two separate issues. If you save the bean in the session, change it, and then read it later, you should read the new property values, Hibernate or no Hibernate. That makes me think you have a bug somewhere...?
Then — hibernateSession.save() always creates a new object in the database. You want saveOrUpdate().
HTH, ~ml
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
