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.
We held a NetBeans platfrom certified training in Bonn. Useres had 6.7.1 installed on Windows. Everytime we created new TopComponents using the wizard it failed for some of the users. The wizard completes but the application fails at runtime. We found out that three bundle entries are missing: CTL_DemoAction=Demo CTL_DemoTopComponent=Demo Window HINT_DemoTopComponent=This is a Demo window We checked different conditions and made sure, that all files including bundle and layer were saved before starting the wizard. We also tried with and without having a layer file registered before starting the wizard. None of these tests revealed any pattern or helped to resolve the issue. It's hard to reproduce and we couldn't find a common pattern, but it failed consistently in about 1 out of 6 tries. So it might be some race condition. I made it a P1, because it's the most basic wizard that every user uses in every tutorial and probably on a daily basis. Giving trainings is almost impossible like this. We had to switch to regular Java SE projects for some sessions and imported modules as jars to workaround this.
Yes. I agree P1 is appropriate. A big problem with this issue is that it doesn't happen all the time. But there seems to be a race condition problem. The bundle is not updated at the end of the Window Component wizard, in some cases. It has never happened to me under Ubuntu. But it happened to several people under Windows during the course mentioned above by Toni.
I just remembered that there was an additional issue most likely related to this, because it happened again right now on my mac installation of 6.7.1: I've created a new Module and a TopComponent and the Wizard failed to add a dependency to utilities api (while adding the bundle entries correctly), so this import from the TopComponent template causes a compiler error: import org.openide.util.NbBundle;
We have seen this bug for Windows XP and Windows Vista (most of them a single core and one notebook with a dual core CPU). NetBeans was installed on a local drive.
there are many wrong things in the IDE, not all of them are P1, please see: http://wiki.netbeans.org/BugPriorityGuidelines Obviously here the workaround is to add the missing bundle keys.
agreed, it's a P2, sorry I didn't check the Priority Guidelines...
Simple workaround, and not known to be reproducible (I was not able to reproduce on XP) -> P3. I don't see anything in the code which would suggest a possible race condition. Does the final wizard panel say that Bundle.properties is to be modified, or not? Are there any errors in your log? If you can reproduce you may need to run the IDE under a debugger to see what is happening. Issue with dep on openide.util may be unrelated, probably better to file separately.