[eclipselink-users] Order of mapping initialization error in EclipseLink

[Zeb Ford-Reitz <Zeb.Ford-Reitz@xxxxxxxxx>]

Hello,

I'm encountering a problem with EclipseLink 2.3 RC1 that I did not 
encounter in EclipseLink 2.2.

The problem involves multiple levels of inheritance and 
"preDeleteMappings". The resulting error is a foreign key violation in a 
join table when committing the removal an entity with a ManyToMany 
association.

The source of the problem seems to be missing preDeleteMappings, which 
would remove the necessary entry from the join table before removing the 
entity itself. Essentially, the order in which the mappings are 
initialized (and post-initialized) causes several of our entites to 
contain the preDeleteMappings from their corresponding direct parents, 
but *not* from all of their ancestors.

Is this a known issue? If so, is it expected to be fixed in the near 
future? If not, can anyone suggest a workaround?

Thanks for your time.

With best regards,
Zeb Ford-Reitz

--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig

Tel.: +49-531-24330-0
Fax:  +49-531-24330-99
http: www.bredex.de

Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature