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

Jive JIRA Integration (JIRA) issues at jboss.org
Wed Apr 15 02:02:19 EDT 2015


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

Jive JIRA Integration updated AS7-783:
--------------------------------------
    Forum Reference: https://developer.jboss.org/message/925570#925570


> 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 was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list