I am having an issue in a multi server BlazeDS environment using a module. I have server 1 with a client application that loads a module on server 2. The services-config.xml has seems to be overwritten when the module loads, which means when I go back to the client application it is now using the services-config.xml for the module which is incorrect and causes error (because the client is expecting its own service configuration).
I currently have a work around in place where I remove the default channel in the module and specify endpoints from a custom config file. Has anyone else experience this issues and is there a better work around than manually specifiy endpoitns in remote objects?