Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] New values on a @OneToMany attribute gets persisted even no cascading is specified

På tirsdag 20. august 2013 kl. 14:34:34, skrev Tom Ware <tom.ware@xxxxxxxxxx>:
Hi Andreas,

  I am surprised you see the attendees cascaded without the cascade setting.   What does your test case do exactly?  What other mappings are there in CalendarEntry?  Do any of them potentially reference CalendarAttendee either directly or through other objects?
 
Attached is a test-case showing Message.partList is cascaded on create, but not on update.
 
I've tested with EL 2.5.1-SNAPSHOT, 2.5.0 and 2.4.2 and all behave the same so it seems this is by design?
 
Care to shed som light on this?
 
Thanks.
 
--
Andreas Joseph Krogh <andreak@xxxxxxxxxxxx>      mob: +47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc
 

Attachment: eclipselink-collection-persisted-without-merge.zip
Description: Zip archive


Back to the top