]
Daniel Azarov commented on JBIDE-7302:
--------------------------------------
I think this problem is similar with JBIDE-7299. There were two rename participants. If
user tries to rename name to name1 one participant does it correctly but another
participant adds one more '1' to name.
This problem was fixed while working on JBIDE-7299.
Problem with Refactor>Rename field in JSF KickStart project when
"Rename getter ...", "Rename setter ..." are checked
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7302
URL:
https://jira.jboss.org/browse/JBIDE-7302
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.0.M2
Environment: JBT trunk, Windows XP, JDK 1.6.0_21
Reporter: Snjezana Peco
Assignee: Daniel Azarov
Fix For: 3.2.0.Beta2
Attachments: GWTRefactorRename.log, RefactorRename.log
Steps to reproduce:
- create a JSF KickStart project
- start the JBoss AS and verify that the application runs correctly
- right-click the name property and call Refactor>Rename
- rename the property to name1, check "Update References", "Rename getter
...", "Rename setter ..."
- click OK
You will get a NPE (attached is RefactorRename.log).
After fixing the NPE (the fix is trivial; the NPE was introduced a few days ago), you
will face the following issues:
- the GWT Rename participants fail and are disabled (this is not a JBT problem; attached
is GWTRefactorRename.log)
- hello.jsp and inputUserName.jsp contain the user.name11 value.
The problem can't be reproduced in JBDS 4.0.0.Beta1.
The problem can be reproduced using the JBT trunk with and without GWT plugins.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: