UML Profile for CORBA Avatar
  1. OMG Specification

UML Profile for CORBA — Closed Issues

  • Acronym: CORP
  • Issues Count: 6
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
CORP-7 Change the VMM CORP 1.0b1 CORP 1.0 Resolved closed
CORP-6 Name of the model element for CORBAUnions CORP 1.0b1 CORP 1.0 Resolved closed
CORP-5 Add long double to the coverage of CORBA primitive types. CORP 1.0b1 CORP 1.0 Resolved closed
CORP-4 The UML 1.4 RTF may tighten the definition of a UML profile. CORP 1.0b1 CORP 1.0 Resolved closed
CORP-3 Namespace rules CORP 1.0b1 CORP 1.0 Resolved closed
CORP-2 The spec. doesn't say precisely which version of CORBA it is targeted to CORP 1.0b1 CORP 1.0 Resolved closed

Issues Descriptions

Change the VMM

  • Key: CORP-7
  • Legacy Issue Number: 3733
  • Status: closed  
  • Source: David Frankel Consulting ( David Frankel)
  • Summary:

    Issue: The VMM elements derived from CORBAWrapper need not be stereotypes of
    Class; Classifier would suffice. Cleaning this up would require a small
    rearrangement of the VMM. This only affects abstract stereotypes, so it
    doesn't change how one actually models.

    Recommendation: Change the VMM accordingly.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    resolved
  • Updated: Mon, 9 Mar 2015 00:40 GMT

Name of the model element for CORBAUnions

  • Key: CORP-6
  • Legacy Issue Number: 3732
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    The name of the model element for CORBAUnions may conflict with
    legitimate member names of the union.

    Recommendation: Instead of specifying a naming convention for the model
    element representing a switch, define a stereotype for a switch and use this
    stereotype to denote that a model element represents a switch. There will
    need to be one stereotype that extends AssociationEnd and one that extends
    Attribute, because the model element representing a switch is an
    AssociationEnd if the switch's type is non-primitive, and is an Attribute if
    the switch's type is primitive.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    resolved
  • Updated: Mon, 9 Mar 2015 00:40 GMT

Add long double to the coverage of CORBA primitive types.

  • Key: CORP-5
  • Legacy Issue Number: 3731
  • Status: closed  
  • Source: David Frankel Consulting ( David Frankel)
  • Summary:

    Issue: The submission's coverage of CORBA primitive types (section 6.5.1.1)
    does not cover the long double primitive type.

    Recommendation: Add long double to the coverage of CORBA primitive types.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    long double will be added to the set of primitives in the same style as long long.
  • Updated: Mon, 9 Mar 2015 00:40 GMT

The UML 1.4 RTF may tighten the definition of a UML profile.

  • Key: CORP-4
  • Legacy Issue Number: 3730
  • Status: closed  
  • Source: David Frankel Consulting ( David Frankel)
  • Summary:

    Recommedation: If possible, synchronize the FTF report with the UML RTF
    report.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    I have no way to resolve this issue, and I suggest we close this issue without further action.
  • Updated: Mon, 9 Mar 2015 00:40 GMT

Namespace rules

  • Key: CORP-3
  • Legacy Issue Number: 3729
  • Status: closed  
  • Source: David Frankel Consulting ( David Frankel)
  • Summary:

    Issue: Namespace rules have been changed in the latest CORBA core
    specification. Specifically, a parent and child can't have the same name.
    This restriction holds only for children and does not hold for grandchildren
    and more distant descendants.

    Recommendation: Fix the formal constraints about namespace containment
    specified in the submission.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    An English constraint and equivalent OCL expression will be inserted to reflect this IDL constraint.
  • Updated: Mon, 9 Mar 2015 00:40 GMT

The spec. doesn't say precisely which version of CORBA it is targeted to

  • Key: CORP-2
  • Legacy Issue Number: 3728
  • Status: closed  
  • Source: David Frankel Consulting ( David Frankel)
  • Summary:

    Recommendation: Specify this (probably CORBA 2.4) and flag IDL features that
    the submission covers but that haven't been made available yet. (Since
    local has been placed in 2.4, attributes raising exceptions is the only
    feature that falls into this category). The conformance language for
    forward engineering tools should be correspondingly tightened.
  • Reported: CORP 1.0b1 — Wed, 28 Jun 2000 04:00 GMT
  • Disposition: Resolved — CORP 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Mon, 9 Mar 2015 00:40 GMT