Community
Participate
Working Groups
1. Create a general project called "dot.test". 2. Add a service and a RUIHandler. 3. Add the service to the DD as a REST service. 4. Now go to the RUI tab and deselect 'Deploy all Rich UI Handlers' and select the handler you created. 5. Copy the DD file and paste it into the same location. In my case I now had two files: "dot_test.egldd" and "Copy of dot_test.egldd". 6. Refactor > Rename the service. It updated "Copy of dot_test.egldd" but not "dot_test.egldd". 7. Refactor > Rename the handler. It updated "Copy of dot_test.egldd" but not "dot_test.egldd".
If you delete the files, they are removed from "Copy of dot_test.egldd" but not from "dot_test.egldd"
I think we should update all the dd files in the same project. I'm setting the priority to p3 meaning it's not a must have for 0.7.
Is it reasonable to put service/handler binding in more than one DD file?
Yes, you might use one DD to deploy the services, and another DD to deploy the RUIHandlers. Users can have as many DDs as they want.
I mean the fact that you put the same service binding in different DD files is reasonable or not?
Whether it's reasonable or not there's nothing to stop you from doing that, so refactoring should handle it. I'm sure some business out there has a case where they want some services on server1 (external) and other services (including a couple of the same as before) on server2 (internal).
Okay, will handle the scenario you described here
RefactoringExecutionStarter
Verified
