In past discussions it seemed unlikely that we would support XML deployments. This was for the following reasons:
- The file would have to specify module configuration inline for it to even work (there is no more flat classpath in AS7) [and be polluted with other various AS internal info]
- Configuration is no longer a "deployable" notion. The domain config contains all admin focused configs and supports runtime updates. This includes which subsystems are available
- Code must be associated with it to really be worth being a deployment, so why not just bundle the code with the deployment? Even some kind of templating/scripting would likely be better represented as multiple files.
- Everything you can do with an XML file can be done with an archive containing the XML file
Is there a strong case for it that was missed?