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.
I created a bean, and a form to allow it to be edited. Imported the bean into the form with "Choose Bean". Minor problem there - it denies the existence of a bean which has been written but not yet compiled. So build, and do the Choose Bean. Then the main event: Add a new property to the bean. It does not show up in the form designer, even if you clean and build the project. The least I've had to do is to close and re-open the project. On one occasion even that didn't seem to be enough and I had to delete Netbeans' index directory. I first noticed this on 6.8beta, which I had on my home Ubuntu machine. I upgraded to 6.8 and the problem was still there. I've just tried it at work on 6.8 Windows. Still there.
Usually you just need to recompile the project and reload the form and it should work.
> Minor problem there - it denies the existence of > a bean which has been written but not yet compiled. I don't see any problem there. You, of course, have to have your bean/component compiled to be able to add it into (and see inside of) the designer. > Then the main event: Add a new property to the bean. > It does not show up in the form designer, even > if you clean and build the project. Did you reload (or closed and reponed) the form? I am sorry, I am not able to reproduce this issue. It would be great if you can provide _exact_ steps to reproduce. Thank you in advance.
It seems if I close the frame window, recompile the bean, then open the frame again that actually updates it (do you have compile-on-save on?) That's pretty inconsistent with the behaviour of Netbeans editors generally where auto-completion etc. responds to code changes immediately. Are you taking the data from the class database or looking at the class files? It seems to be pretty natural to be editing both the form and it's backing bean at the same time.
> That's pretty inconsistent with the behaviour of Netbeans editors > generally where auto-completion etc. responds to code changes immediately. There is a HUGE difference between editors and GUI builder. Editors are working with text only, the GUI builder works with classes. The object that you see in the GUI builder are instances of your classes. That's why we need to have your classes (re-)compiled and the form reloaded. > Are you taking the data from the class database or looking at the class files? We are using ClassLoader provided by ClassPath (+ some IDE/project related classloader tweaks), see ProjectClassLoader and FormClassLoader if you are interested.