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 102024 - Rename should be disabled for files such as faces-config.xml
Summary: Rename should be disabled for files such as faces-config.xml
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P4 blocker (vote)
Assignee: _ potingwu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-20 21:21 UTC by Chary Kanaparthi
Modified: 2008-09-02 21:26 UTC (History)
0 users

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 Chary Kanaparthi 2007-04-20 21:21:44 UTC 
Rename context menu option should be disabled on certain files such as
faces-config.xml, MANIFEST.MF... from Projects &
Files View ?

for example : When faces-config.xml is renamed whole project will go mad
Comment 1 _ sandipchitale 2007-04-21 01:05:37 UTC 
The noides in project logical view provides these actions.
Comment 2 Radko Najman 2007-04-27 07:05:37 UTC 
The mentioned actions are not provided by the project's logical view. It is a
responsibility of each module which implements DataNode for a given file to
override canRename() method.

In my opinion it is more P4 than P2 but decreasing to P3 and reassigning to the
responsible developer to decide. Our users never reported this problem and I
would say they never will. Each web developer knows for what are these files
good and that they should not be renamed and a smart developer will never do it.

I can imagine a situation when the user wants to rename one of these files -
rename the existing file to use it as a backup file and then create a new file
with different entries e.g. for testing purposes.

Reassigning to jsf subcomponent for faces-config.xml. It should be investigated
also for Struts config files.
Comment 3 Jiri Prox 2007-09-17 21:39:29 UTC 
Obsolete milestone, please reevaluate
Comment 4 Andrei Badea 2007-10-08 16:33:29 UTC 
Don't see this as a big priority. I can imagine an user renaming e.g. faces-config.xml to faces-config.bak.xml and
copying a new faces-config.xml in WEB-INF to replace the old one.
Comment 5 Erno Mononen 2007-10-08 19:00:36 UTC 
Additionally, nothing mandates that a JSF configuration file has to be named "faces-config.xml". You can define the 
configuration files(s) in web.xml using the javax.faces.CONFIG_FILES init parameter. Please see section 10.4.2 in the 
JSF specification for more info. I think this issue is invalid - perhaps we could even have some support for renaming a 
JSF config file, but that doesn't seem like a high priority feature.
Comment 6 Jiri Prox 2008-04-11 01:04:45 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 7 _ potingwu 2008-09-02 21:26:28 UTC 
> nothing mandates that a JSF configuration file has to be named "faces-config.xml"

Yes, this is true that a JSF project should/can always use "faces-config.xml". I.e., the IDE should not force users to
use it. It should be an option for the users.