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 55515 - Renaming a JavaBean Field should trigger refactoring
Summary: Renaming a JavaBean Field should trigger refactoring
Status: RESOLVED DUPLICATE of bug 47625
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-25 00:40 UTC by Vince Kraemer
Modified: 2007-04-03 18:02 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 Vince Kraemer 2005-02-25 00:40:56 UTC 
If you expand a java class node you get to the
Bean Patterns node.

This node lists the fields associated with a class
(from a JavaBean perspective).

The right click menu for these fields has a Rename.

Currently, rename just works locally in the file
(and performs many of the same tasks that
refactoring seems to).  A rename of the node
should actually trigger a real refactoring request.
Comment 1 Jan Becicka 2005-05-20 09:51:07 UTC 

*** This issue has been marked as a duplicate of 47625 ***
Comment 2 Vince Kraemer 2005-05-20 17:32:52 UTC 
I guess this is a variation of the issue.  The difference is where the user
"starts" from.  In most of the other issues marked as a dup, the user is in the
java editor.  In this case the user is in the explorer.

Please don't forget that case.