Project: springxd
Issue XD-2988: Issues with custom modules when using module configuration
SpringXD seems to think that a module exists if there is a module configuration present. There is also an issue of having to restart the node when theres been a problem with uploading/removing a module. When using SpringXD in single node on windows, i uploaded a custom module and then added a folder and property file for it in the module configuration directory as specified in the documentation. When i went to delete the module using the command in the SpringXD admin console, it would say that it was successfull, but when then listing the modules, it would still be listed. If i tried to upload a new version of that same module, i would get an error stating that module already existed with the same name. I would check the custom modules directory and my jar would not be there. I would then have to manually delete the module configuration directory and restart SpringXD before being able to upload a new module, having to replace my module configuration each time. Seems like there are three things wrong here: * should the presence of a module configuration alone inform SpringXD of a modules existence? * should one have to delete a module configuration before uploading a new version of the module? * when getting module deletion/upload errors, should one have to restart spring xd node to get it to allow the upload again?
Story points: 1