${taskforce.name} Avatar
  1. OMG Task Force

UML-CORBA & CCM FTF — All Issues

  • Key: CCCMP
  • Issues Count: 16
Open Closed All
All Issues

Issues Descriptions

Bounded string attribute of struct/union/valuetype/interface is not mapped

  • Key: CCCMP-16
  • Status: open  
  • Source: Airbus Group ( Oliver Kellogg)
  • Summary:

    Section 8.1.2 defines stereotypes CORBAAnonymousSequence and CORBAAnonymousArray for mapping sequence/array attributes of struct/union/valuetype/interface without a dedicated typedef.
    However, an equivalent CORBAAnonymousString stereotype is not defined.
    Thus it is not obvious how to map e.g.

      struct struct_with_anon_bounded_str {
        string<32> anon_bounded_str;
      };
    
      union union_with_anon_bounded_str switch (boolean) {
        case TRUE:
          string<32> anon_bounded_str;
      };
    
      valuetype valuetype_with_anon_bounded_str {
        public string<32> anon_bounded_str;
      };
    
      interface interface_with_anon_bounded_str {
        attribute string<32> anon_bounded_str;
      };
    
  • Reported: CCCMP 1.0 — Wed, 20 Mar 2019 09:27 GMT
  • Updated: Mon, 8 Apr 2019 16:47 GMT

Extended UML metamodel derivations of <>

  • Key: CCCMP-15
  • Status: open  
  • Source: Airbus Group ( Oliver Kellogg)
  • Summary:

    The UML Profile for CORBA and CCM on page 47 states:

    The extended UML metamodel contains an abstract stereotype <<CORBATemplate>>, which is a generalization of <<CORBAString>>, <<CORBAWstring>>, and <<CORBASequence>> stereotypes.

    The part about «CORBAString» and «CORBAWstring» inheriting from «CORBATemplate» does not fit with figure 8.7 on page 42 which shows that those stereotypes inherit from «CORBABounded».

    According to the class diagram, the sentence should be:

    The extended UML metamodel contains an abstract stereotype <<CORBATemplate>>, which is a generalization of <<CORBAArray>> and <<CORBASequence>> stereotypes.
    
  • Reported: CCCMP 1.0 — Fri, 9 Feb 2018 13:02 GMT
  • Updated: Mon, 12 Feb 2018 10:28 GMT

Section: 8.1.2, Figure 8.12

  • Key: CCCMP-14
  • Legacy Issue Number: 11010
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    Figure 8.12: A first attribute should have type A::B rather than B with clarification

  • Reported: CCCMP 1.0b1 — Wed, 16 May 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    For more clarification the Figure 8.12 should be updated

  • Updated: Sat, 7 Mar 2015 04:15 GMT

Section: 8.1.2

  • Key: CCCMP-13
  • Legacy Issue Number: 11009
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    The replacement text, first bullet: "Array ... multidimensional array dimension (e.g.: “index”=n, m)." is unclear why there are two ways to represent array index. Do all arrays representations have a Tag for index, even if the attribute multiplicity is used in the case of one dimensional array. It should state that the multiplicity for a multi dimension array is the product of all the dimension values (e.g, integer [2][3] has multiplicity 6. Also, it needs to be clarified whether the member attribute is in row major or collumn major order

  • Reported: CCCMP 1.0b1 — Wed, 16 May 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see resolution to issue 10835

  • Updated: Sat, 7 Mar 2015 04:15 GMT

Section: 7.3.3

  • Key: CCCMP-12
  • Legacy Issue Number: 10983
  • Status: closed  
  • Source: Objective Interface Systems ( Victor Giddings)
  • Summary:

    The last sentence of the bullet defining the Basic Stream type: "The data is consumed and produced by component implementation logic as octet sequences, unless the basic stream type". The last clause seems misplaced, and should probably be dropped

  • Reported: CCCMP 1.0b1 — Mon, 7 May 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    Resolution: Delete the last clause

  • Updated: Sat, 7 Mar 2015 04:15 GMT

Section: 7.2.10

  • Key: CCCMP-11
  • Legacy Issue Number: 10982
  • Status: closed  
  • Source: Objective Interface Systems ( Victor Giddings)
  • Summary:

    The following constraints in 7.2.10 are incorrect: [1] A ConstantDef must be defined in a Container [2] A TypedefDef must be defined in a Container [6] An ExceptionDef must be defined in a Container [8] An InterfaceDef must be defined within a ModuleDef [9] A ValueDef must be defined within a ModuleDef Each of these can be defined as "global scope" (as is acknowledged in 7.2.3: "Modules can contain any definition that can appear at global scope (type, constant, exception, and interface definitions)"

  • Reported: CCCMP 1.0b1 — Mon, 7 May 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see above

  • Updated: Sat, 7 Mar 2015 04:15 GMT

Section: 3 Normative References

  • Key: CCCMP-10
  • Legacy Issue Number: 10981
  • Status: closed  
  • Source: Objective Interface Systems ( Victor Giddings)
  • Summary:

    The list of Normative References contains the CORBA Component Model Specification, Version 4.0 twice, but does not have a normative reference to the CORBA specification

  • Reported: CCCMP 1.0b1 — Mon, 7 May 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see above

  • Updated: Sat, 7 Mar 2015 04:15 GMT

clarification about relationships of specifications needed

  • Key: CCCMP-8
  • Legacy Issue Number: 10837
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    Initiated by Frank Pilhofer (Mercury Computer Systems: At the moment there are two OMG specification documents: the UML Profile for CORBA (formal/02-04-01) and the UML Profile for CORBA Component Model (formal/05-07-06). More clarification is needed about relationships between mentioned above two specs and this current final adopted spec. What are the differences between all profiles and migration rules from one to another?

  • Reported: CCCMP 1.0b1 — Wed, 21 Mar 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see above

  • Updated: Sat, 7 Mar 2015 04:14 GMT

More clarification text about order of CORBAStruct members is needed

  • Key: CCCMP-9
  • Legacy Issue Number: 10838
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    More clarification text about order of CORBAStruct members is needed

  • Reported: CCCMP 1.0b1 — Wed, 21 Mar 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see resolution to issue 10836

  • Updated: Sat, 7 Mar 2015 04:14 GMT

Section: 8.1.2 p. 40

  • Key: CCCMP-7
  • Legacy Issue Number: 10836
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    Initiated by Tom Rutt (Fujitsu) "According to the metamodel for UML (uml super fig 7-12 and 7-13) the OwnedAttribute association end of class and data type is ordered, and includes both "attributes" and "association ends". So from UML point of view the Struct mapping is ok in the current spec. (However some tools have trouble ordering across attributes and association ends). The FTF may decide to not use the association version of containment for Struct members which are themselves complex types

  • Reported: CCCMP 1.0b1 — Wed, 21 Mar 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Sat, 7 Mar 2015 04:14 GMT

Section: 8.1.2 p. 44

  • Key: CCCMP-6
  • Legacy Issue Number: 10835
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    Initiated from Tom Rutt (Fujitsu): "Something similar to Sequences could be done for array mappings as well."

  • Reported: CCCMP 1.0b1 — Wed, 21 Mar 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see above

  • Updated: Sat, 7 Mar 2015 04:14 GMT

Section: 8.1.2

  • Key: CCCMP-5
  • Legacy Issue Number: 10834
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Julia Reznik)
  • Summary:

    Initiated from Tom Rutt (Fujitsu: "The sequence mapping needs either fixing or clarification. I am still concerned about the complexity and yet incompleteness of the profile mapping for CORBA sequences and arrays. Suggestion: AnonymousSequence types are named by concatenation containing type "::" "m"<n> , where n is the member number of the anonymous sequence in containing type, e. g bar::m2 for second member of Struct bar (P. 31, Figure 8.15). Also I suggest to represent the sequence element values as a multivalued attribute with lower bound 0 and upper bound = sequence size or "*". This seems to work and is much easier to understand. Also, it requires NO NEW TAGGED VALUES for Sequencies."

  • Reported: CCCMP 1.0b1 — Wed, 21 Mar 2007 04:00 GMT
  • Disposition: Resolved — CCCMP 1.0
  • Disposition Summary:

    see below

  • Updated: Sat, 7 Mar 2015 04:14 GMT

Inconsistent capitalization of <>

  • Key: CCCMP-4
  • Legacy Issue Number: 18380
  • Status: open  
  • Source: Airbus Group ( Oliver Kellogg)
  • Summary:

    For the stereotype designating IDL "typedef", the UML Profile for CORBA
    v1.0 (02-04-01) uses the capitalization "CORBATypedef".
    The UML Profile for CORBA and CCM v1.0 (08-04-07) sometimes uses the
    same capitalization but also uses the capitalization "CORBATypeDef"
    (notice the capital "D".)
    For compatibility with the UML Profile for CORBA, I suggest replacing
    all occurrences of "CORBATypeDef" by "CORBATypedef".

  • Reported: CCCMP 1.0 — Mon, 21 Jan 2013 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Section: 8.2.1 - 2

  • Key: CCCMP-2
  • Legacy Issue Number: 11159
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Yann Tanguy)
  • Summary:

    P. 51 . The CORBAUses stereotype has a property "multiple" of type PrimitiveKind P. 53 . The CORBAUses stereotype has a property "isMultiple" of type boolean. This looks like a naming and type inconsistency between diagram and tabular representation of the stereotype. If this is the case and isMultiple is really typed boolean, PrimitiveKind becomes useless (I did not find any other use of PrimitiveKind in the profile). If not (I mean PrimitiveKind is the wanted type), it may be better to type the "multiple" property with the "CORBAPrimitive" stereotype instead of creating and using an enumeration like PrimitiveKind.

  • Reported: CCCMP 1.0 — Wed, 18 Jul 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Section 9 of UML Profile for CORBA and CCM

  • Key: CCCMP-3
  • Legacy Issue Number: 12359
  • Status: open  
  • Source: Objective Interface Systems ( Victor Giddings)
  • Summary:

    Chapter 9 should be clearly marked as non-normative. Noted during smsc review. Thus, formal document number not available

  • Reported: CCCMP 1.0 — Mon, 31 Mar 2008 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT

Section: 8.1.2

  • Key: CCCMP-1
  • Legacy Issue Number: 11158
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Yann Tanguy)
  • Summary:

    Litteral of the enumeration PrimitiveKind are prefixed with "CORBA" or "Corba", instead of "CORBA" (upper case) for all litterals

  • Reported: CCCMP 1.0 — Wed, 18 Jul 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:59 GMT