Currently our AS7 kit will place our REST, WebDAV and CMIS WAR files into the "deployments" directory (with a ".dodeploy" file). This works, but can be a problem in three situations:
- When the kit is installed but the server is started with a configuration that does not use the ModeShape subsystem, the server still tries but fails to deploy/start the ModeShape WARs (since they expect a running ModeShape subsystem). The server does run properly, but this is messy.
- When the kit is installed but the server's configuration is changed with an improper ModeShape subsystem configuration, the ModeShape subsystem will not start. The server still tries but fails to deploy/start the ModeShape WARs (since they expect a running ModeShape subsystem).
- The proposed AS7.2 patching feature will not work with our installation mechanism. That wiki page's "Patching Deployments" section states that the ideal mechanism is to have the subsystem (e.g., our ModeShapeExtension implementation) to deploy these artifacts upon startup. (See also the extensions page).
Therefore, we should change our kit so that the ModeShape subsystem does deploy the WARs upon startup. Obviously it should only deploy them if not already deployed. And, we probably should add configuration attributes that specify which services should be auto-deployed (all three should be auto-deployed by default).
This will improve our user experience, and will also be compatible with the proposed patching facility.