Support of <ImplementationArtifacts> within <NodeTemplate> element

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • CSD2
    • Affects Version/s: CSD2
    • Component/s: Spec
    • None
    • Hide

      A node type may provide the implementation artifacts for the operations of its interface. We should support the ability to override extend these implementation artifacts at the referencing node template level.

      Show
      A node type may provide the implementation artifacts for the operations of its interface. We should support the ability to override extend these implementation artifacts at the referencing node template level.
    • Hide

      This issue resolved by motion on 2012-04-05 (see minutes):
      Motion: Approve changes in WD05 (contained in the file http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45575/TOSCA-v1.0-wd05.zip) and close TOSCA-5 as RESOLVED.Implementation artifacts

      Show
      This issue resolved by motion on 2012-04-05 (see minutes): Motion: Approve changes in WD05 (contained in the file http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45575/TOSCA-v1.0-wd05.zip ) and close TOSCA-5 as RESOLVED.Implementation artifacts

      Today, a <NodeType> element supports the definition of <DeploymentArtifacts> representing executable entities of the node type itself. These deployment artifacts may be overridden or extended or provided first time by another <DeploymentArtifact> element of the referencing <NodeTemplate>.

      This mechanism should be supported for <ImplementationArtifacts> too: A node type may define the implementation artifacts for its operations, but a node template derived from this node type should be able to actually provide an implementation artifact, override an implementation artifact or extend the set of implementation artifacts. For this purpose, the proposal is to add an <ImplementationArtifacts> element to the <NodeTemplate> element as sibling of the <DeploymentArtifacts> element.

            Assignee:
            Frank Leymann (Inactive)
            Reporter:
            Frank Leymann (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: