|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
I renamed a service called Calculator to CalculatorService. As a result the CalculatorImpl class was renamed to CalculatorImplService, which I think should be CalculatorServiceImpl instead.
|
|
Description
|
I renamed a service called Calculator to CalculatorService. As a result the CalculatorImpl class was renamed to CalculatorImplService, which I think should be CalculatorServiceImpl instead. |
Show » |
|
Cosmetics
Open
Normal
Inconvenient service rename
I have found an error in the behavior of the rename-refactoring in the context of a GWT application. I will submit a JIRA. It may be causing you anguish, so I describe it here.
I take a shared point of reference the the sample application provided under new-
>Google Web Toolkit->GWT sample application. Start a new project and load that. Call it MySampleApplication.The short version is that if you refactor-rename the .java class named MySampleApplication which is created, you'll break the application. This is because the refactoring renames (without giving you an option not to) a certain line in interface:
public interface MySampleApplicationService extends RemoteService
more exactly, this line:
((ServiceDefTarget) app).setServiceEntryPoint(GWT.getModuleBaseURL() +
"mySampleApplication.MySampleApplication/MySampleApplicationService");
and even more exactly second occurrence of MySampleApplication in the line:
"mySampleApplication.MySampleApplication/MySampleApplicationService")
my rename looks like this:
"mySampleApplication.BigMistake/MySampleApplicationService");
So that's the bad behavior in a nutshell.