[
https://issues.jboss.org/browse/AS7-4529?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on AS7-4529:
------------------------------------------
note, I assume here that .failed will be generated for the failed deployments.
a "failure-causes-rollback="false"" attribute for
the filesystem scanner
------------------------------------------------------------------------
Key: AS7-4529
URL:
https://issues.jboss.org/browse/AS7-4529
Project: Application Server 7
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found
at startup is deployed in one operation and if one deployment fails all is rolled back
resulting in some rather bad usability issues - especially at development time, but even
also at production time for those using file deployments.
Suggestion on irc was that there could be an option on the file scanner (possibly false
by default?) to say that failure causes rollback.
Individual deployments could then still fail, but at least not everything would be
rolledback and it would still allow proper interdependent deployments to work.
--
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