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.
Properties set through form connection (specifically through 'property', but perhaps others also) do not persist if the Form is added to the palette. For example, suppose a JPanel form which has been given a titled border. The border's text is set to the panel's name through Form Connection -> Property. If this panel is now added to the palette and included in another form, the established connection does not carry over. I believe this behaviour is not necessary when connecting two properties of the same object.
The example you mention is rather a problem of the order in which the properties are set in the generated code. In this case setBorder is generated before setName, so when the border's title is set, the name is null. This is a problem of an one-off setting. We should either implement a way to fix the order of properties, or (2) allow to easily establish a "live" connection that updates on changes and does not depend on the order. In 6.0 we could use beans binding for that. (1) Letting the user to change the order of the properties setters of a component in the code would be useful (e.g. the "Code Customizer" dialog could be used for that), but would not really solve this issue - the order dependency can be between components as well. Maybe the properties set via property or method connection should be simply generated at the end of the initComponents method - after all things are set up. (2) Would require some better UI integration of binding with the property editors. E.g. having the binding as one of the property editor modes, or something like adding a checkbox "Live connection" to the existing property connection editor which would generate binding code behind the scene automatically.
*** Issue 87430 has been marked as a duplicate of this issue. ***
still experiencing this issue in IDE 6.1