Urs Beeli Messages: 488 Registered: October 2012 Location: Bern, Switzerland
I've seen the same thing using Eclipse's Refactor->Rename mechanism to change the name of a service and/or interface. It seems not to update the plugin.xml occurences of the class name. However, as this leads to warnings it is fairly easy to pick up on, so not tragic in my point of view. I haven't actually tried to rename a service/interface using the Scout SDK so am not sure what the behaviour is there.
In my opinion renaming in general is a bit of a pain in Scout, as there so many classes generated when e.g. creating a form. However when renaming the form none of these generated classes are changed by the framework. I am still working on a pretty small POC with Scout and have not too much time pressure, so it is annoying but somehow manageable. But regarding using Scout in a real development project this might lead to some lost time and a potential source of errors. And if you want to create later a class with the same name, it does not work because the not renamed services/formData/etc classes already exist but would have to be created in order to create a form.