From: <leg...@at...> - 2003-06-25 21:21:50
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-149 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-149 Summary: Using Sets Before Fully Initialized causes NullPointerException Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Bill Dudney Created: Wed, 25 Jun 2003 4:21 PM Updated: Wed, 25 Jun 2003 4:21 PM Environment: JDK 1.4.1 Description: one-to-man from A -> B A.addB(B foo) { if(null != foo) { set_of_bs.add(foo); foo.setA(this); } } B.setA(A bar) { a = bar; if(null != a && !a.getBs().contains(this)) { a.addB(b); } } I'm not sure why but the tempList in the net.sf.hibernate.collection.Set ends up being null at some point during initialization. endRead is being called twice, the first time its ok the second time it throws a NullPointerException. I'm not sure this is a bug with Hibernate or if I should not be maintaining the backwards pointers in this way. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |