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 was moved from Bugtraq: #4677939 (Submitter: vince.kraemer@sun.com) Here is the exception: java.util.MissingResourceException: Can't find bundle for base name org.netbeans.modules.form.Bundle, locale en at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773) at java.util.ResourceBundle.getBundle(ResourceBundle.java:661) at org.openide.util.NbBundle.getBundle(NbBundle.java:337) at org.openide.util.NbBundle.getBundle(NbBundle.java:272) at org.netbeans.core.windows.WorkspaceImpl.getDisplayName(WorkspaceImpl.java:232) at org.netbeans.core.windows.WorkspaceSwitcher.addNew(WorkspaceSwitcher.java:251) at org.netbeans.core.windows.WorkspaceSwitcher.<init>(WorkspaceSwitcher.java:83) at org.netbeans.core.windows.MainWindow.showWindow(MainWindow.java:195) at org.netbeans.core.Main.initializeMainWindow(Main.java:291) at org.netbeans.core.NonGui.run(NonGui.java:578) at org.netbeans.core.Main.run(Main.java:213) at org.openide.TopManager.initializeTopManager(TopManager.java:120) at org.openide.TopManager.getDefault(TopManager.java:81) at org.netbeans.core.Main.main(Main.java:346) at org.netbeans.core.TopThreadGroup.run(TopThreadGroup.java:87) at java.lang.Thread.run(Thread.java:536)
I am not able reproduce this exception. But I found similar behaviour: * disable form module * restart IDE * Now, enable module throws exception (and name for GuiEditing Workspace is wrong - after restart IDE is name for GUI editing all right): java.util.MissingResourceException: Can't find bundle for base name org.netbeans.modules.form.Bundle, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:694) at java.util.ResourceBundle.getBundle(ResourceBundle.java:661) at org.openide.util.NbBundle.getBundle(NbBundle.java:337) at org.openide.util.NbBundle.getBundle(NbBundle.java:272) at org.netbeans.core.windows.WorkspaceImpl.getDisplayName(WorkspaceImpl.java:232) at org.netbeans.core.windows.WorkspaceSwitcher.addNew(WorkspaceSwitcher.java:251) at org.netbeans.core.windows.WorkspaceSwitcher.propChange(WorkspaceSwitcher.java:180) at org.netbeans.core.windows.WorkspaceSwitcher.access$000(WorkspaceSwitcher.java:46) at org.netbeans.core.windows.WorkspaceSwitcher$1.run(WorkspaceSwitcher.java:125) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) at java.awt.EventQueue.dispatchEvent(EventQueue.java:443) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:190) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:144) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:130) at java.awt.EventDispatchThread.run(EventDispatchThread.java:98)
> Can't find bundle for base name > org.netbeans.modules.form.Bundle Well, if form module is uninstalled... I guess window system should do something this.
reassigne
-> ttran
it works fine now in NB 3.4 dev builds
*** Issue 25061 has been marked as a duplicate of this issue. ***
It does not seem to work fine - see issue 25061 reported against build 20020621.
window system folks, please make sure that deserialization of TC can deal with the situation when the bundle is gone (module has been uninstalled). The question of course is what text to use then because uninstalling a module does not necessarily mean deleting a workspace. I suggest we cache the localized workspace name and use it in such a situation
Sometimes when Form Editor is disabled GUI Editing workspace is not removed as it should because it is defined in Form Editor module layer. It seems it is problem of data system. I filed issue #25092. *** This issue has been marked as a duplicate of 25092 ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.
A CLOSED issue mistakenly moved into a NEW state... closing again (step 1).
x
*** This issue has been marked as a duplicate of 25092 ***
Closing again.