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 180825 - Rename attribute does not properly work after some refactoring actions
Summary: Rename attribute does not properly work after some refactoring actions
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: J Bachorik
Depends on: 181679 181818
Blocks: 173077
  Show dependency tree
Reported: 2010-02-17 04:33 UTC by Alexandr Scherbatiy
Modified: 2010-03-12 07:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

JavaFX project (42.05 KB, application/zip)
2010-02-17 04:34 UTC, Alexandr Scherbatiy

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2010-02-17 04:33:15 UTC
NetBeans-JavaFX-Soma: #156

  Product Version         = NetBeans IDE Dev (Build 201002160200) (#6c8c2438b925)
  Operating System        = Windows XP version 5.1 running on x86
  Java; VM; Vendor        = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc.

Steps to reproduce:

- Open the attached project
- Go to the 'javafxset.core' package
- Refactor-Rename the 'STree' class to 'STree2'
- Refactor-Rename the 'STreeNode' class to 'STreeNode2'

- Open the STreeNode2 class 
- Refactor->Rename the 'handle' property to 'handle2'

- Clean and build the project

JavaFXSet\src\javafxset\core\JavaFXSet.fx:107: cannot find symbol
symbol  : function handle(function(:Object):void)
location: class javafxset.core.STreeNode2
1 error
Comment 1 Alexandr Scherbatiy 2010-02-17 04:34:05 UTC
Created attachment 94222 [details]
JavaFX project
Comment 2 J Bachorik 2010-03-05 07:57:44 UTC
Comment 3 Alexandr Scherbatiy 2010-03-09 09:00:51 UTC
The issue is still reproduced in build 
NetBeans-JavaFX-Soma:  #179 Mar 9, 2010 9:29:41 AM
Comment 4 J Bachorik 2010-03-09 09:16:09 UTC
Caused by #181679. Please, check again when the fix for that issue makes it into the build.
Comment 5 Alexandr Scherbatiy 2010-03-09 09:19:48 UTC
I didn't use the Refactor->Move action in this issue.
Comment 6 J Bachorik 2010-03-09 09:42:27 UTC
My bad. Of course, this is a different case ...
Comment 7 J Bachorik 2010-03-11 02:54:00 UTC
There is some problem with caching and the fact that certain JavaFX classes may be affected by the refactoring but not necessarily be changed physically by that.

Filed and issue to Parsing&Indexing -
Comment 8 J Bachorik 2010-03-11 11:02:39 UTC
As a side-effect of re-implementing the javafx indexer as a CustomIndexer is the fact that the indexer doesn't suffer from staled parser results problem.
Comment 9 Alexandr Scherbatiy 2010-03-12 07:40:08 UTC
verified in NetBeans-JavaFX-Soma: #182