DEPL 1.0 MAILINGLIST Avatar
  1. OMG Issue

DEPL — Misuse of ComponentPackageReference for Implementation Dependencies

  • Key: DEPL-3
  • Legacy Issue Number: 5955
  • Status: open  
  • Source: Zuehlke Engineering ( Frank Pilhofer)
  • Summary:

    The ComponentImplementationDescription class references the
    ComponentPackageReference class to express dependencies on
    implementations that have to exist in the target environment.
    Because of the different semantics, a new class should be
    introduced instead.

    Proposed resolution:

    In section 3.10, "Common Elements", add an ImplementationDepen-
    dency class as follows:

    ImplementationDependency

    Description

    Expresses a dependency that an implementation has on the
    target environment. Before this implementation can be
    deployed, an application of the required type must exist
    (it must have finished launching) in the target environment.

    Attributes

    • requiredType: String The interface type of which an
      application must exist.

    Associations

    No associations.

    Constraints

    No constraints.

    Semantics

    When launching an application, the ExecutionManager and
    DomainApplicationManager verify that applications of the
    required type are already executing.

    In section 3.4, "Component Data Model", in the Associations
    section for the ComponentImplementationDescription class, update
    the type of the dependsOn association to be ImplementationDepen-
    dency:

    • dependsOn: ImplementationDependency [*] Expresses a depen-
      dency on another package; implementations of the referenced
      interfaces must be deployed in the target environment before
      this implementation can be deployed.

    In section 3.8, "Execution Data Model", in the Associations
    section for the DeploymentPlan class, update the type of the
    dependsOn association to be ImplementationDependency.

  • Reported: DEPL 1.0b1 — Thu, 19 Jun 2003 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT