DEPL 4.0 MAILINGLIST Avatar
  1. OMG Issue

DEPL4 — Distinguish Node vs. Component Exec Parameters in Deployment Plan

  • Key: DEPL4-29
  • Legacy Issue Number: 8979
  • Status: closed  
  • Source: Zuehlke Engineering ( Frank Pilhofer)
  • Summary:

    The resolution for issue 6435 split the former "execution
    parameters" into "node execution parameters" and "component
    execution parameters" within the Component Data Model, by
    extending the MonolithicImplementationDescription element
    to have separate "nodeExecParameter" and "componentExec-
    Parameter" property lists.

    However, the resolution neglected to make a similar change
    to the Execution Data Model – the MonolithicDeployment-
    Description element in the Deployment Plan only has a single
    list of "execParameter" properties.

    This should be changed to be in sync with the Component
    Data Model.

    Proposed resolution:

    In section 6.8.3.3 (MonoliticDeploymentDescription
    associations), remove the "execParameter" association.

    Instead, add the following two associations:

    nodeExecParameter: Property[*]
    Execution parameters that are passed to the target
    environment. Copied from the MonoliticImplementation-
    Description.
    componentExecParameter: Property[*]
    Execution parameters that are passed to the primary
    artifact. Copied from the MonoliticImplementation-
    Description.

  • Reported: DEPL 1.0 — Fri, 26 Aug 2005 04:00 GMT
  • Disposition: Resolved — DEPL 4.0
  • Disposition Summary:

    No Data Available

  • Updated: Wed, 11 Mar 2015 01:53 GMT