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 185422 - refactoring of a JSF managed bean should refactor XHTML files
Summary: refactoring of a JSF managed bean should refactor XHTML files
Status: NEW
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal with 2 votes (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on: 137467
Blocks: 173299
  Show dependency tree
 
Reported: 2010-05-04 10:16 UTC by Jindrich Sedek
Modified: 2014-10-03 06:20 UTC (History)
2 users (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 Jindrich Sedek 2010-05-04 10:16:45 UTC 
Create new JSF managed bean
add a property to the bean
use the bean and it's property in XHTML file:
<c:out value="#{newJSFManagedBean.propX}"/>


invoke refactor/Rename on 'propX' -> 'The refactoring cannot be applied at this context' message is shown.

It would be greate to refactor the property name in this case (field name, getter method, setter method and all the usages in all XHTML files)
Comment 1 Erno Mononen 2010-08-03 13:56:58 UTC 
Taking over as I'm currently working on related refactorings.
Comment 2 hans_adler 2014-09-30 17:13:22 UTC 
Should this feature request be marked closed?

I have found my way here because this functionality now exists in my installation, but has an annoying bug that messes up my xhtml files if a replacement is done more than once and the new property name is shorter than the old one.

(I haven't found a report for this bug yet. Please let me know if one exists and I am just too stupid to find it. Otherwise I will research this a little further and report it myself.)

I should note that I am working in a complex environment that I did not set up by myself. It's possible that the functionality and the bug is actually in a plugin that someone else installed.
Comment 3 Petr Jiricka 2014-09-30 22:04:21 UTC 
Assigning to Martin Fousek.
Comment 4 Martin Fousek 2014-10-03 06:20:59 UTC 
(In reply to hans_adler from comment #2)
> Should this feature request be marked closed?
> 
> I have found my way here because this functionality now exists in my
> installation, but has an annoying bug that messes up my xhtml files if a
> replacement is done more than once and the new property name is shorter than
> the old one.

We should keep this issue opened. We offer to users such a refactoring but only from side of the ManagedBean. The XHTML side returns still the same message 'The refactoring cannot be applied at this context'.

> (I haven't found a report for this bug yet. Please let me know if one exists
> and I am just too stupid to find it. Otherwise I will research this a little
> further and report it myself.)
> 
> I should note that I am working in a complex environment that I did not set
> up by myself. It's possible that the functionality and the bug is actually
> in a plugin that someone else installed.

AFAIK there is not such bug entered in the bugzilla. Please report your issue - ideally with some steps how to reproduce that and with attached messages log. As you mentioned it can be other plugin issue, but let's evaluate your issue firstly. Please open the issue as a new report. Thanks a lot.