[Hibernate-JIRA] Created: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[Hibernate-JIRA] Created:...

[Hibernate-JIRA] Created: (HV-156)...

Daniel Wellman (JIRA)

Sunday, 22 April 2007 Sun, 22 Apr '07

11:36 p.m.

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

sebastien kurz (JIRA)

Tuesday, 9 October Tue, 9 Oct

6:26 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] sebastien kurz commented on HHH-2584: ------------------------------------- I have also a strange behavior on map : child = em.find(...,key); em.remove(child); works, but child = em.find(...,key); parent.getMap().get(key); em.remove(child); will fail !!! i.e. when the map is initialized, the removing fails even when directly deleting the entities.

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Mattias Jiderhamn (JIRA)

Friday, 12 October Fri, 12 Oct

12:59 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Mattias Jiderhamn commented on HHH-2584: ---------------------------------------- Why has this patch still not been submitted to CVS?

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Christian Bauer (JIRA)

4:28 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Christian Bauer updated HHH-2584: --------------------------------- Comment: was deleted

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Diego Pires Plentz (JIRA)

Monday, 15 October Mon, 15 Oct

5:05 a.m.

New subject: [Hibernate-JIRA] Resolved: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Diego Pires Plentz resolved HHH-2584. ------------------------------------- Assignee: Diego Pires Plentz Resolution: Duplicate

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Diego Pires Plentz Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

SoWeLie (JIRA)

Monday, 5 January Mon, 5 Jan

8:42 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] SoWeLie commented on HHH-2584: ------------------------------ This seems to still be an issue in 3.3.1. When I call remove on an uninitialized map, the object is not removed. If I do something like call the values method, then try the remove, the object is removed properly.

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Diego Plentz Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Steve Ebersole (JIRA)

Friday, 20 November Fri, 20 Nov

9:20 p.m.

New subject: [Hibernate-JIRA] Reopened: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Steve Ebersole reopened HHH-2584: ---------------------------------

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Diego Plentz Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Steve Ebersole (JIRA)

9:20 p.m.

New subject: [Hibernate-JIRA] Assigned: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Steve Ebersole reassigned HHH-2584: ----------------------------------- Assignee: Steve Ebersole (was: Diego Plentz)

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Steve Ebersole (JIRA)

9:22 p.m.

New subject: [Hibernate-JIRA] Updated: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Steve Ebersole updated HHH-2584: -------------------------------- Fix Version/s: 3.5 3.3.x

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Fix For: 3.3.x, 3.5 Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Steve Ebersole (JIRA)

Saturday, 21 November Sat, 21 Nov

3:58 a.m.

New subject: [Hibernate-JIRA] Closed: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Steve Ebersole closed HHH-2584. ------------------------------- Resolution: Fixed

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Fix For: 3.5, 3.3.x Attachments: persistentmap_remove.patch Time Spent: 53 minutes Remaining Estimate: 0 minutes This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Mattias Jiderhamn (JIRA)

Friday, 23 April Fri, 23 Apr

6:08 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Mattias Jiderhamn commented on HHH-2584: ---------------------------------------- This bug has been fixed for lazy associations, BUT mappings which are both lazy and inverse still have this issue (in 3.3.2)

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Fix For: 3.3.x, 3.5.0-Beta-3 Attachments: persistentmap_remove.patch Time Spent: 53m Remaining Estimate: 0h This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Gail Badner (JIRA)

9:11 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584?page=c... ] Gail Badner commented on HHH-2584: ---------------------------------- Mattias, if this is still an issue with maps that are lazy and inverse, please open a new issue with a test case.

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Fix For: 3.3.x, 3.5.0-Beta-3 Attachments: persistentmap_remove.patch Time Spent: 53m Remaining Estimate: 0h This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

Mattias Jiderhamn (JIRA)

Wednesday, 28 April Wed, 28 Apr

1:24 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

...

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.2.1, 3.2.2, 3.2.3 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Assignee: Steve Ebersole Fix For: 3.3.x, 3.5.0-Beta-3 Attachments: persistentmap_remove.patch Time Spent: 53m Remaining Estimate: 0h This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly.

5173

days inactive

6275

days old

hibernate-issues@lists.jboss.org

Manage subscription

12 comments

8 participants

tags (0)

participants (8)

Christian Bauer (JIRA)
Daniel Wellman (JIRA)
Diego Pires Plentz (JIRA)
Gail Badner (JIRA)
Mattias Jiderhamn (JIRA)
sebastien kurz (JIRA)
SoWeLie (JIRA)
Steve Ebersole (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[Hibernate-JIRA] Created: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map