This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 210789

Summary: Reload Form With Beans Binding Scrambles Form Up
Product: guibuilder Reporter: MackSix
Component: BindingAssignee: issues@guibuilder <issues>
Status: RESOLVED FIXED    
Severity: normal CC: rsmon
Priority: P1    
Version: 7.2   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Attachments: Project to use for reproduction.
Screenshot of Dialog Box

Description MackSix 2012-04-06 03:22:59 UTC
Created attachment 117916 [details]
Project to use for reproduction.

Test Project based on http://wiki.netbeans.org/TS_61_BeanBinding#Test_suite:_Advanced_test item #8 Validators

1.) Open attached Beans Binding test project.
2.) Open both java files in editor
3.) View NewJFrame.java in Design mode.
4.) Right click on root "Form NewJFrame" in Navigator and choose to "Reload Form".

Dialog pops up - Error in loading component: [JFrame]->targetLabel and targetLabel loses it's text. See Attached Screenshot. 

5.) Click Cancel and form is messed up and cannot display in Design Mode. 
6.) Close the project and reopen it and everything is fixed.

This work OK in v7.0.1 but not in v7.1.1 or 

Product Version: NetBeans IDE Dev (Build 201204050400)
Java: 1.7.0_03; Java HotSpot(TM) Client VM 22.1-b02
System: Windows Vista version 6.0 running on x86; Cp1252; en_US (nb)

Regression - should be marked P1.
Comment 1 MackSix 2012-04-06 03:23:42 UTC
Created attachment 117917 [details]
Screenshot of Dialog Box
Comment 2 Jan Stola 2012-04-06 08:40:07 UTC
This issue was introduced during separation of some binding functionality into a separate module. Any form using Beans Binding failed to reload since then because binding support was not cleared correctly during the reload. I have fixed that.

Modified file: http://hg.netbeans.org/jet-main/rev/1009656c608f
Comment 3 Tomas Pavek 2012-11-27 17:49:56 UTC
*** Bug 208238 has been marked as a duplicate of this bug. ***