- This topic has 6 replies, 4 voices, and was last updated 16 years, 7 months ago by
.
-
Posts
-
When I choose to refactor a method in a java class, the refactor dialog does not find any of the JSP usages to update. All my classes and JSPs are in a single project that is MyEclipse-web-enabled.
I figure this was done on purpose 😉 You shouldn’t use Java code in JSP pages. Sun and about the whole Java community have been advocating against doing this for years now.
Nevertheless, I would be a nice extra feature to have. Most (older) projects have some JSP pages in them where some programmer felt it was necesarry to use Java on it.
smolloy,
I cannot reproduce this problem either using the same test project I sent you earlier to try. Could you try it in my test project, selecting all the check boxes in the refactor menu and see if it works?I found that if you “Close” (context menu option) the project in the “Navigator” tab, then “Open Project”, that the JSP references are rebuilt and from then forward it seems to work fine. This fix also works to restore the “Find References…” not searching JSPs. Something about the JSP index of usages gets rebuild when you close/open the project in the workspace.
A couple of times the refactoring created rubbish in my JSP files. Formatting was destroyed, but much worse imports were ruined. Instead of being replaced fully with a new package name, the package name in the JSP after refactoring ended up being some mix of the old and new name. E.g. suppose the old name was com.java.foo and the new was com.java.bar, the name in the imports would be com.java.fobaro or something like that.
The last time I tried this was with MyEclipse 6.0, so maybe its better now.
