[OASIS Issue Tracker] (CAMP-206) Assembly Instantiation Hierarchies

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64850#comment-64850 ] 

Michael Norman commented on CAMP-206:
-------------------------------------

The resolution to this would involve merging the notions of Component and Assembly, choosing one name (e.g. Assembly) and then having Assemblies with many child Assemblies and at most one parent Assembly.  We are not going to resolve this quickly in the spec.  

However there's nothing to stop it being added by extension, even though that means the Spec isn't carrying much of the relevant semantics.  Suggest we defer this one.

> Assembly Instantiation Hierarchies
> ----------------------------------
>
>                 Key: CAMP-206
>                 URL: https://issues.oasis-open.org/browse/CAMP-206
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Assignee: Anish Karmarkar
>            Priority: Trivial
>
> We have touched on this in one call, and this is a placeholder to make sure we close out the discussion.  In CAMP we have a Component and an Assembly. This is effectively an instantiation hierarchy of depth 2, and 2 is never a good number to have in your code.  It seems intuitively that weshould have a hierarchy of arbitrary depth by nesting assembly instantiation.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)