[jboss-jira] [JBoss JIRA] (WFLY-364) a "failure-causes-rollback="false"" attribute for the filesystem scanner

[Emanuel Muckenhuber (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emanuel Muckenhuber reassigned WFLY-364:
----------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Brian Stansberry)

    
> a "failure-causes-rollback="false"" attribute for the filesystem scanner
> ------------------------------------------------------------------------
>
>                 Key: WFLY-364
>                 URL: https://issues.jboss.org/browse/WFLY-364
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Max Rydahl Andersen
>            Assignee: Emanuel Muckenhuber
>             Fix For: 8.0.0.CR1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira