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 44258 - Refactoring & rename action: tag library functions changes are not propagated.
Summary: Refactoring & rename action: tag library functions changes are not propagated.
Status: RESOLVED DUPLICATE of bug 168033
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-03 02:24 UTC by Ana.von Klopp
Modified: 2009-09-30 13:50 UTC (History)
1 user (show)

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 Ana.von Klopp 2004-06-03 02:24:01 UTC 
Create a tag library inside a web module. 
Create a Java class with a method that returns a 
string for example. 
Add a function declaration that refers to the 
method. 

Use the refactoring "rename class" operation, or 
rename class from the explorer - the TLD is not 
updated. 

Use the refactoring "rename method" operation, or 
rename it from the method menu in the explorer - 
the TLD is not updated. 

This means that the UI action supplied by the IDE 
can change a working web module into one that does 
not run.
Comment 1 Milan Kuchtiak 2004-06-09 15:24:29 UTC 
Right, but there was no UI specification for this (refactoring) feature.
Moreover, there is no API in refactoring module that would help us.
Comment 2 Ana.von Klopp 2004-06-09 16:46:24 UTC 
I am OK with not fixing this in NB 4.0, but I disagree with the 
classification of this as an enhancement. It's a bug - the fact that 
the APIs did not allow you to do this was an error in the process of 
communicating requirements, it doesn't turn it into an enchancement. 

If there is a UI action for refactoring and it potentially leaves a 
previously working application in a non-working state, then surely 
that's a bug...
Comment 3 Petr Jiricka 2004-06-09 17:05:28 UTC 
I must say I agree with the classification of this as enhancement.
Previously, we had the rename action which also left the application
in a non-working state.

Or, if you use a class name in a .properties file and do refactoring
on the class, this will also leave the app in a non-working state.

The important point though is that WebApps/J2EE refactoring was not
planned for in the PCD. just Java refactoring.
Comment 4 _ ludo 2004-06-09 18:28:03 UTC 
I would see this as a bug since the IDE has exposed user actions that
do not work.
The user will not really care about the PCD at this stage. As a user
of NetBeans 3.6, I know I can do Web Apps.
In annoucements of new Features of NB4.0, I hear about Refactoring.
My user expectation is that refactoring works with Web App in NB4.0.
I would agree for being waived for D but not for promo E where it has
to be seen as a defining feature, but I am concerned this is not
considered a bug. 

Is it explicitely written in the PCD that refactoring will not work
for Web Apps? The initial Studio plans was to have refactoring for the
entire J2EE area, based on NB4.0. I would assume that the Web App area
would have been delivered from NB4.0
Maybe I am wrong...
Comment 5 Petr Jiricka 2009-09-30 13:50:49 UTC 
Duplicate of issue 168033.

*** This issue has been marked as a duplicate of 168033 ***