Re: [Hibernate] dependent object that is a reference to another hibernate object

2003-02-05 Thread Justen Stepka
m: "Justen Stepka" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 04, 2003 8:41 PM Subject: Re: [Hibernate] dependent object that is a reference to another hibernate object > Yup.. that's how I got the

Re: [Hibernate] dependent object that is a reference to another hibernate object

2003-02-05 Thread Justen Stepka
rrect way to have the cacades setup? Thanks, Justen Stepka - Original Message - From: <[EMAIL PROTECTED]> To: "Justen Stepka" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 04, 2003 7:59 PM Subject: Re: [Hibernate] dependent object that is

Re: [Hibernate] dependent object that is a reference to another hibernate object

2003-02-05 Thread Gavin . King
If you don't want the save() to cascade, you should set cascade="none" or cascade="delete" on the association to User. (Also, as long as unsaved-value is correct, the save() will cascade to an update() of the User, which is okay usually.)

[Hibernate] dependent object that is a reference to another hibernate object

2003-02-05 Thread Justen Stepka
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 i