[jira] [Commented] (ARIES-1050) Revisit the use of coordinations in order to take advantage of the deployment manifest optimizations.

["John Ross (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681729#comment-13681729 ] 

John Ross commented on ARIES-1050:
----------------------------------

Coordination use during install is currently optimized. InstallAction is only called for an explicit install operation (i.e. Subsystem.install is called by a client). The coordination is created and passed along to the ResourceInstaller->SubsystemResourceInstaller, where any embedded subsystems (i.e. children of the explicitly installing subsystem) are also installed. The same coordination will be used for the entire operation, and deployment manifests will not be saved until the coordination ends.
                
> Revisit the use of coordinations in order to take advantage of the deployment manifest optimizations.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1050
>                 URL: https://issues.apache.org/jira/browse/ARIES-1050
>             Project: Aries
>          Issue Type: Improvement
>          Components: Subsystem
>            Reporter: John Ross
>
> ARIES-1034 introduced an optimization where the saving of the deployment manifest is delayed when a coordination is present. All subsystem operations affecting the deployment manifest should be revisted and make use of coordinations in order to take advantage of this change.

--
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