« Return to Thread: Cascade delete bug (221389) fixed in 2.0 line but not 1.1 line?

Re: Cascade delete bug (221389) fixed in 2.0 line but not 1.1 line?

by Russell Teabeault :: Rate this Message:

Reply to Author | View in Thread

Sorry.  I also forgot to mention that the problem we seem to have bumped into is a NullPointerException from the following in UnitOfWorkImpl.java

if(descriptor.hasMappingsPostCalculateChanges()) {
int size = descriptor.getMappingsPostCalculateChangesOnDeleted().size();
...
It appears that the one map is being tested but a different map is being used.  This seems to have been fixed in trunk with r3826 and we are wondering the best way to resolve this in the 1.1 line.

Thanks,

Russell Teabeault

On Wed, Jun 24, 2009 at 4:08 PM, Russ Teabeault <rteabeault@...> wrote:
It seems that this cascade delete bug was fixed in the 2.0 line but not in the 1.1 line.  We uncovered this bug today and are wondering if there are plans for creating a 1.1.2 patch?

------------------------------------------------------------------------
r3826 | gyorke | 2009-03-31 14:54:49 -0600 (Tue, 31 Mar 2009) | 4 lines

Cascade Delete bug  221389
reviewed by James Sutherland, Andrei Ilitchev, Tom Ware

Simple update missed during merge.
------------------------------------------------------------------------


_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

 « Return to Thread: Cascade delete bug (221389) fixed in 2.0 line but not 1.1 line?