[
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...
Deployment scanner service should use a separate operation for each
deployment
------------------------------------------------------------------------------
Key: AS7-783
URL:
https://issues.jboss.org/browse/AS7-783
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.1.0.CR1
The scanner is creating a single composite op for all deployments encountered in a scan,
rather than individual ops. The effect is failures in on deployment results in rolling
back the others.
This makes some sense when users change things after startup, since multiple changes
within one scan are probably related to each other. But it's not the correct behavior
at startup, since multiple apps may not be interrelated.
--
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