CORBA Component Model Avatar
  1. OMG Specification

CORBA Component Model — All Issues

  • Acronym: CCM
  • Issues Count: 11
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

3.2.7 Compositions with Managed Storage

  • Key: CORBA34-63
  • Legacy Issue Number: 5871
  • Status: closed  
  • Source: Opus Software ( Alexandre Ricardo Nardi)
  • Summary:

    Need to reflect the change in the PSS specification, in which the catalog is not user-defined anymore. The example and the cidl syntax (chapter 2) need to be changed too.

  • Reported: CCM 3.0 — Tue, 25 Feb 2003 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

3.2.7 Compositions with Managed Storage

  • Key: CORBA35-59
  • Legacy Issue Number: 5871
  • Status: open  
  • Source: Opus Software ( Alexandre Ricardo Nardi)
  • Summary:

    Need to reflect the change in the PSS specification, in which the catalog is not user-defined anymore. The example and the cidl syntax (chapter 2) need to be changed too.

  • Reported: CCM 3.0 — Tue, 25 Feb 2003 05:00 GMT
  • Updated: Wed, 1 Feb 2023 21:59 GMT

EnterpriseComponent should have a get_servant method

  • Key: CORBA34-54
  • Legacy Issue Number: 6672
  • Status: closed  
  • Source: National Lab. on Distributed Processing of P.R.China ( Deng Bo)
  • Summary:

    The EnterpriseComponent should have a get_servant method. When creating component or facet reference of service or session component, the first step is creating the object reference and associating its PortableServer::ObjectId with servant. Currently, the container manages executor, but the EnterpriseComponent interface does not provide a mechanism to get servant. The method would be very useful as it means the container can use executor to get servant, which is not possible now.

    Resolution:

    Replace the following text in formal/02-06-05 on page 3-39

    module Components { local interface EnterpriseComponent {}; };

    with

    module Components { local interface EnterpriseComponent

    { Servant get_servant() raises (CCMException); }

    ; };

    and add the operation description

    get_servant

    The get_servant operation returns a reference to the servant.

  • Reported: CCM 3.0 — Thu, 4 Dec 2003 05:00 GMT
  • Disposition: Deferred — CORBA 3.4
  • Disposition Summary:

    Deferred

    This proposal was generated automatically by request of the Task Force Chair Adam Mitz.

  • Updated: Wed, 1 Feb 2023 21:59 GMT

EnterpriseComponent should have a get_servant method

  • Key: CORBA35-50
  • Legacy Issue Number: 6672
  • Status: open  
  • Source: National Lab. on Distributed Processing of P.R.China ( Deng Bo)
  • Summary:

    The EnterpriseComponent should have a get_servant method. When creating component or facet reference of service or session component, the first step is creating the object reference and associating its PortableServer::ObjectId with servant. Currently, the container manages executor, but the EnterpriseComponent interface does not provide a mechanism to get servant. The method would be very useful as it means the container can use executor to get servant, which is not possible now.

    Resolution:

    Replace the following text in formal/02-06-05 on page 3-39

    module Components { local interface EnterpriseComponent {}; };

    with

    module Components { local interface EnterpriseComponent

    { Servant get_servant() raises (CCMException); }

    ; };

    and add the operation description

    get_servant

    The get_servant operation returns a reference to the servant.

  • Reported: CCM 3.0 — Thu, 4 Dec 2003 05:00 GMT
  • Updated: Wed, 1 Feb 2023 21:59 GMT

definition of the stereotype CORBAPrimaryKey

  • Key: CCMP-1
  • Legacy Issue Number: 7628
  • Status: open  
  • Source: Fraunhofer FOKUS ( Dr. 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

Facet and Receptacles (ports)

  • Key: CCMP-3
  • Legacy Issue Number: 7632
  • Status: open  
  • Source: ANSYS, Inc. ( 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 ( Dr. 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

Event ports

  • Key: CCMP-4
  • Legacy Issue Number: 7633
  • Status: open  
  • Source: ANSYS, Inc. ( 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

Association needed

  • Key: CCMP-6
  • Legacy Issue Number: 7635
  • Status: open  
  • Source: ANSYS, Inc. ( 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, Inc. ( 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

Issues related to CCM's XML descriptors: chapter 69.4.5.4

  • Key: CORBA3-124
  • Legacy Issue Number: 5493
  • Status: closed  
  • Source: INRIA ( Philippe Merle)
  • Summary:

    chapter 69.4.5.4
    "The information obtained by (...) it allows component assembly
    tools to decide WHAT ports
    on a component are capable (...)"
    it seems that the word "which" would be better than "what" in
    this sentence

  • Reported: CCM 3.0 — Mon, 15 Jul 2002 04:00 GMT
  • Disposition: Resolved — CORBA 3.0.2
  • Disposition Summary:

    Replace "what" by "which".

  • Updated: Fri, 6 Mar 2015 20:58 GMT