facebook

Changing JSP file name is not reflected in faces-config.xml

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #238911 Reply

    pds1602
    Member

    Two problems:

    1) If I rename a JSP file that is referred to in the faces-config.xml file, by using refactor rename, faces-config.xml is not updated.

    2) To fix this I try and change the name of the JSP file in the outline…right click on JSP file and edit. This creates a new page in the JSF design view and the original page stays the same – its not changed.

    What we need is for the refactoring to work both ways or if its not possible to refactor from myeclipse, to have refactor…rename work for JSP pages in faces-config.xml (and maybe struts-config as well). If that’s not possible, at least a rename in the JSF outline should actually change the name of the file in faces-config, not create a new one.

    #238983

    Riyad Kalla
    Member

    Currently the refactoring is not hooked into the XML files, but that is something we are focusing on in 4.1 and or 5.0 if it gets pushed back. sorry for the inconvenience.

    #239177

    pds1602
    Member

    @support-rkalla wrote:

    Currently the refactoring is not hooked into the XML files, but that is something we are focusing on in 4.1 and or 5.0 if it gets pushed back. sorry for the inconvenience.

    Hi,

    That takes care of the first issue but not the second. Changing the filename in the outline should do just that, not create an additional file.

    #239183

    Riyad Kalla
    Member

    #2) I’m not following what you are describing here. You cannot refactor from the Outline View, so I am assuming you mean the Package View, however when I refactored the name of a JSP I had open in the designer the name was changed correctly in the package view (the editor tab retains the old name which is a bug) but no 2nd file is created as you described it.

    #239239

    pds1602
    Member

    @support-rkalla wrote:

    #2) I’m not following what you are describing here. You cannot refactor from the Outline View, so I am assuming you mean the Package View, however when I refactored the name of a JSP I had open in the designer the name was changed correctly in the package view (the editor tab retains the old name which is a bug) but no 2nd file is created as you described it.

    You will need a project that already has a valid faces-config file created manually or through myeclipse, doesn’t matter. Go into the faces-config graphical editor. Select one of the jsp files. Go to the outline. The file will be selected. Right click on it and select edit. This pops up a myeclipse navigation rule wizard dialog box. Change the name in this dialog. A new node is created instead of renaming the existing one.

    If you use the graphical editor to create a page and then rename the page, without leaving the editor, it is renamed correctly.

    #239254

    Riyad Kalla
    Member

    What you are doing here is editing the navigation rules, this is not the same as a refactoring-rename action. The navigation rules can be any string you want them to be, there is no hard-tie between what you type here and page created in your project.

    The edit dialog is fairly straight forward in that it does not offer a refactor action, do it’s likely not a good idea to use it for that purpose (in your case you end up with disjoint file names).

    #239307

    pds1602
    Member

    OK, well then it’s what you would call an inconsistent UI. It should not allow you to enter a filename unless it already exists. Yet it does allow this. So, if the page has just been created it does change the name, but not if it exists already. This is hopelessly confusing.

    You have to allow either one or the other.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: Changing JSP file name is not reflected in faces-config.xml

You must be logged in to post in the forum log in