RE: [Hibernate] Flush behavior

Huh? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Bauer Sent: Sunday, November 20, 2005 12:58 PM To: Hibernate development Subject: Re: [Hibernate] Flush behavior On Nov 20, 2005, at 6:48 PM, Gavin King wrote: > Hibernate cascades the save

Re: [Hibernate] Flush behavior

On Nov 20, 2005, at 6:48 PM, Gavin King wrote: Hibernate cascades the saveOrUpdate() operation, EJB3 cascades the persist() operation. They should and are quite different. But why are persist (and possibly merge) only cascaded at call time and not at flush time, if I use the Session API? I

RE: [Hibernate] Second level cache and mappedBy side of a FK one-to-one

This would be quite difficult to implement. Internally, a one-to-one property-ref looks nothing like a collection. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Sunday, November 20, 2005 2:28 AM To: Hibernate development Subject

RE: [Hibernate] specific annotation for collection of elements

IMO, the @OneToMany annotation should not be used for collections of value-typed objects. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Sunday, November 20, 2005 3:41 AM To: Hibernate development Subject: [Hibernate] specific annot

RE: [Hibernate] Flush behavior

Negative. Hibernate cascades the saveOrUpdate() operation, EJB3 cascades the persist() operation. They should and are quite different. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Bauer Sent: Sunday, November 20, 2005 3:43 AM To: Hibernate

[Hibernate] Flush behavior

http://opensource.atlassian.com/projects/hibernate/browse/HHH-1181 They should be synchronized, if we have the same methods on Session and on EM, they should do the same. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified

[Hibernate] specific annotation for collection of elements

It started from turin42: i read the spec and the docs and i've got a hard time explaining the abuse of @OneToMany is this how it is going to look like in EJB 3.1? epbernard: Nothing is specified for such things in EJB3 nor even globally designed What do you mean by @OneToMany abuse turin42: @One

[Hibernate] Second level cache and mappedBy side of a FK one-to-one

Owner side mappedBy side In this case, the owner side is resolved in cache, and not the mappedBy side (if I load person, employee will be resolved in the 2nd cache, if employee is loaded, person cannot be resolved in the 2nd level cache) But the mapped by side is actually some kind of 1 elem