[ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-783: --------------------------------- Fix Version/s: 7.1.0.Beta2 (was: 7.0.0.CR1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated AS7-783: ---------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) I'm not sure I agree - basically it's a tradeoff between having undesired rollbacks or possible issues due to interrelated deployments being unable to proceed. Maybe it'd be better to support some kind of partial rollback, or something... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.sy... ] jaikiran pai commented on AS7-783: ---------------------------------- I had a patch (and probably still have it on a local branch) which used individual operations for the deployments in the file system deployment directory. IMO, it makes sense to _not_ consider all the deployments in the deployment folder as a single batch, since we never really "advertise" officially (we shouldn't really) that all deployments in the folder are one single application that are dependent on each other. i.e. an unrelated deployment shouldn't affect the deployment of some other application. But I also see the advantage for some applications to deploy a group of deployments as one single batch. So, I had kept aside that patch to think of adding an attribute on the deployment scanner: {code} <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.0"> <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="deployments"/> <!-- Allow deploying the applications in the custom folder as a batch --> <deployment-scanner scan-interval="5000" relative-to="jboss.server.base.dir" path="my-deployments" deploy-as-batch="true"/> </subsystem> {code} Note the use of a deploy-as-batch (optional) attribute. This would allow users to decide how they want to deploy multiple applications. I just haven't found the time to discuss/implement this. If this is something that looks reasonable, then maybe we could have it implemented in some upcoming release? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.sy... ] Emanuel Muckenhuber commented on AS7-783: ----------------------------------------- We should double check that with OSGI - afaik they have something called deployment-sets. Although we don't really support their requirements on the deployment layer either, the closest thing would most likely be a composite operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira