[jboss-jira] [JBoss JIRA] (AS7-783) Deployment scanner service should use a separate operation for each deployment

[Brian Stansberry (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639262#comment-12639262 ] 

Brian Stansberry commented on AS7-783:
--------------------------------------

Jaikiran, if you have the branch, feel free to add a link to it. My main reason for closing this is I don't want to deal with it any time in the next few months, and I don't want to mislead people into working on it. But if work is already done we shouldn't throw it away; we can reconsider when we have time to think about it.
                
> 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: No Release
>
>
> 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