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 78450

Summary: Matisse Update Pack: Refactoring Resource Bundle keys with auto-i18n feature
Product: guibuilder Reporter: Masaki Katakai <masaki>
Component: CodeAssignee: issues@guibuilder <issues>
Status: VERIFIED DUPLICATE    
Severity: blocker CC: jf4jbug
Priority: P2 Keywords: I18N
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Masaki Katakai 2006-06-20 03:57:02 UTC 
NB: 5.0 + Matisse Update Pack
OS: All

I'm using 5.0 + Matisse Update Pack, which was downloaded from UC Beta.
I have a question about refactoring with Automatic Internationalization feature.

1. Run IDE
2. Create a project
3. Create a form
4. Put some components onto the form
5. Enable Automatic Internationalization

Now keys and values are extracted to Bundle.properties, like

NewJPanel.jButton1.text=jButton1
NewJPanel.jButton2.text=jButton2
NewJPanel.jButton3.text=jButton3

Then, I want to rename "NewJPanal" to other.

6. Select "NewJPanel.java" and try Refactor to rename it

filename and variable could be renamed, however, the
keys of properties are still "NewJPanel.....".

Refactoring resource bundle has not been implemented yet?
What is the best way for refactoring with this Automatic
Internationalization feature? We need to give the reasonable
scenario to users, because users often use such refactoring
for GUI.
Comment 1 Jana Maleckova 2006-07-31 10:54:56 UTC 
version changed from dev to 5.0
Comment 2 Tomas Pavek 2006-08-09 16:50:52 UTC 
Neither refactoring of form generated code (issue 48288) nor refactoring of
internationalized data (issue 56549) has been implemented yet.

I think the auto-i18n does not add any new problem to what we know already. The
scenario you mention could be handled better (i.e. rename the keys automatically
- I'd expect doing this with 48288) but nothing actually gets broken - the keys
remain valid and working.

A workaround is to turn off the auto-i18n before changing the form class name,
then turning it on again after the refactoring is done.



*** This issue has been marked as a duplicate of 48288 ***
Comment 3 Pavel Rehak 2006-08-23 13:01:33 UTC 
Marking as verified - this works as designed atm - see issue #48288 for future
development milestones.
Comment 4 Jan Stola 2006-09-20 09:12:54 UTC 
*** Issue 85309 has been marked as a duplicate of this issue. ***
Comment 5 Jan Stola 2006-09-20 15:48:25 UTC 
*** Issue 85309 has been marked as a duplicate of this issue. ***