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 77712 - Unable to run form by Shift+F6
Summary: Unable to run form by Shift+F6
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jan Jancura
URL:
Keywords:
: 93120 126791 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-12 11:01 UTC by Jaromir Uhrik
Modified: 2010-06-07 17:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2006-06-12 11:01:16 UTC 
[NB 5.0 + Matisse GUI Builder JavaOne Update]
It is not possible to run single form file. It is just in case when "Automatic
Internationalization" property of the form is on.
Steps to reproduce:
1. Create j2se project
2. Create new JFrame form
3. Set property "Automatic Internationalization" to true
4. Add some component to the form (e.g. JButton)
5. Change the text on this button by double click on it in form designer
6. Run form file by Shift+F6
Following output is printed:
------------------------------------------%<--------------------------------------
xception in thread "AWT-EventQueue-0" java.util.MissingResourceException: Can't
find resource for bundle java.util.PropertyResourceBundle, key
NewJFrame.jButton2.text
        at java.util.ResourceBundle.getObject(ResourceBundle.java:325)
        at java.util.ResourceBundle.getString(ResourceBundle.java:285)
        at javaapplication38.NewJFrame.initComponents(NewJFrame.java:67)
        at javaapplication38.NewJFrame.<init>(NewJFrame.java:17)
        at javaapplication38.NewJFrame$1.run(NewJFrame.java:135)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
        at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
        at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
------------------------------------------%<--------------------------------------
The workaround is to Build all project first. Then this issue doesn't appear.
This is because by project building the new version of resource bundle is copied
to the build folder.
Comment 1 Tomas Pavek 2006-08-09 14:33:17 UTC 
I don't know what we could do here... You need to build the project, or at least
compile the package.

Maybe java project could do something. Copying all non-java files automatically
whenever running single file? Or providing "Compile" action on non-java files
(for moving to build folder explicitly)?

Reassigning for evaluation...
Comment 2 Tomas Pavek 2007-02-01 14:10:17 UTC 
*** Issue 93120 has been marked as a duplicate of this issue. ***
Comment 3 Tomas Zezula 2007-02-15 13:32:31 UTC 
Maybe build sungle should copy at lest all non java files in the same pacakge.
Comment 4 Jan Becicka 2007-10-17 13:15:22 UTC 
P4. Users usually do build all at least once IMO.
Comment 5 Jiri Prox 2008-04-11 00:52:32 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 6 Quality Engineering 2009-12-21 05:20:21 UTC 
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team
Comment 7 Tomas Pavek 2010-06-07 17:03:54 UTC 
*** Bug 126791 has been marked as a duplicate of this bug. ***