UML Profile for CORBA Components Avatar
  1. OMG Specification

UML Profile for CORBA Components — Open Issues

  • Acronym: CCMP
  • Issues Count: 6
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Association needed

  • Key: CCMP-6
  • Legacy Issue Number: 7635
  • Status: open  
  • Source: Ansys ( Marc Born)
  • Summary:

    Association with <<CORBAManages>> between HomeImplDef and ComponentImplDef is needed, otherwise you can’t navigate and define what HomeImplDef manages what ComponentImplDef.

  • Reported: CCMP 1.0b1 — Mon, 16 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Figure6: associations described Event ports have to be composite associatio

  • Key: CCMP-5
  • Legacy Issue Number: 7634
  • Status: open  
  • Source: Ansys ( Marc Born)
  • Summary:

    Figure6: associations described Event ports have to be composite associations.

  • Reported: CCMP 1.0b1 — Mon, 16 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Event ports

  • Key: CCMP-4
  • Legacy Issue Number: 7633
  • Status: open  
  • Source: Ansys ( Marc Born)
  • Summary:

    Event ports are specified as an UML association, but their names are specified as role names of the association end of the referenced event. It means, the component refers directly to the external event – it’s confusing. Suggestion: Event port (such as Facet and Receptacle) names are the names of the associations.

  • Reported: CCMP 1.0b1 — Mon, 16 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Facet and Receptacles (ports)

  • Key: CCMP-3
  • Legacy Issue Number: 7632
  • Status: open  
  • Source: Ansys ( Marc Born)
  • Summary:

    Facet and Receptacles (ports) are specified as an UML association, but their names are specified as role names of the association end of the referenced interface. It means, the component refers directly to the external interface – it’s confusing and less intuitiv. Suggestion: Facet and Receptacle names are the names of the associations, describing ports.

  • Reported: CCMP 1.0b1 — Mon, 16 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

The (IDL) definition of the example is not correct

  • Key: CCMP-2
  • Legacy Issue Number: 7629
  • Status: open  
  • Source: Fraunhofer FOKUS ( Tom Ritter)
  • Summary:

    The (IDL) definition of the example is not correct. The valuetyp for the key is not allowed to be abstract and it must have at least one public member. Furthermore, this key needs to be derived from Components::PrimaryKeyBase. The picture of the UML model should also be completely shown (i.e. including the member of the primary key). Suggestion: Modify example (IDL and picture)

  • Reported: CCMP 1.0b1 — Fri, 13 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

definition of the stereotype CORBAPrimaryKey

  • Key: CCMP-1
  • Legacy Issue Number: 7628
  • Status: open  
  • Source: Fraunhofer FOKUS ( Tom Ritter)
  • Summary:

    The definition of the stereotype CORBAPrimaryKey makes too strong restrictions. The CORBA Component Model defines a primary key as an ordinary valuetype, which is derived from Components::PrimaryKeyBase. Using the stereotype PrimaryKey would prevent me from using this valuetype in other parts of my application as a plain valuetype (e.g operation parameter). Suggestion: Remove stereotyp CORBAPrimaryKey. Use stereotype CORBAValueDef instead and refomulate the constraints accordingly. (e.g. inheritance)

  • Reported: CCMP 1.0b1 — Fri, 13 Aug 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT