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

QoS for CCM FTF — All Issues

Create Issue
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
QOSCCM-7 Section: 8.7.2 StubContainerInterceptionRegistration has several errors QOSCCM 1.0b1 QOSCCM 1.0b2 Resolved closed
QOSCCM-6 Section: 8.7.2 QOSCCM 1.0b1 QOSCCM 1.0b2 Resolved closed
QOSCCM-8 Section: 8.7.3 QOSCCM 1.0b1 QOSCCM 1.0b2 Resolved closed
QOSCCM-2 Examples QOSCCM 1.0b2 open
QOSCCM-1 Section: 8.6 Derivation of RequestInfo QOSCCM 1.0b2 open
QOSCCM-5 ExtensionComponent and ccm_remove QOSCCM 1.0b1 open
QOSCCM-4 operations in the interface StubContainerInterceptor QOSCCM 1.0b1 open
QOSCCM-3 QoS for CCM ComponentInstallation QOSCCM 1.0b1 open

Issues Descriptions

Section: 8.7.2 StubContainerInterceptionRegistration has several errors

  • Key: QOSCCM-7
  • Legacy Issue Number: 10565
  • Status: closed  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    StubContainerInterceptionRegistration has several errors. In IDL the local interface name is wrong, the register and unregister method names are wrong and have wrong types. In 8.7.2.4 and .5 headers are wrong
  • Reported: QOSCCM 1.0b1 — Fri, 5 Jan 2007 05:00 GMT
  • Disposition: Resolved — QOSCCM 1.0b2
  • Disposition Summary:

    IDL problems have been fixed. Wrong names and headers have been fixed.
    Some other minor typos have been fixed.
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Section: 8.7.2

  • Key: QOSCCM-6
  • Legacy Issue Number: 10564
  • Status: closed  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    Argument of register_server_interceptor must be a ServerContainerInterceptor
  • Reported: QOSCCM 1.0b1 — Fri, 5 Jan 2007 05:00 GMT
  • Disposition: Resolved — QOSCCM 1.0b2
  • Disposition Summary:

    IDL Problems has been fixed.
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Section: 8.7.3

  • Key: QOSCCM-8
  • Legacy Issue Number: 10566
  • Status: closed  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    8.7.3 has several errors, in description, headers, idl, wrong types, interfaces, etc
  • Reported: QOSCCM 1.0b1 — Fri, 5 Jan 2007 05:00 GMT
  • Disposition: Resolved — QOSCCM 1.0b2
  • Disposition Summary:

    Wrong IDL and headers have been fixed.
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Examples

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

    More complete examples that show the actual QoSConstraint structures, the deployment of QoSEnablers, the negotiation, and the use of the COPIs would be really helpful in understanding the spec.

  • Reported: QOSCCM 1.0b2 — Thu, 18 May 2006 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

Section: 8.6 Derivation of RequestInfo

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

    Derivation of RequestInfo Why isn't ContainerClientRequestInfo simply derived (with no extension) from PortableInterceptor::ClientRequestInfo? This would save a step (calling request_info()) in user code. Why isn't ContainerServerRequestInfo simply derived (with no extension) from PortableInterceptor::ServerRequestInfo? This would save a step (calling request_info()) in user code.
  • Reported: QOSCCM 1.0b2 — Thu, 18 May 2006 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

ExtensionComponent and ccm_remove

  • Key: QOSCCM-5
  • Legacy Issue Number: 16253
  • Status: open  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    Can anyone explain why the ExtensionComponent only delivers the
    ccm_remove method and not all the other methods which the
    SessionComponent has?
  • Reported: QOSCCM 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

operations in the interface StubContainerInterceptor

  • Key: QOSCCM-4
  • Legacy Issue Number: 11322
  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Dr. Ansgar Radermacher)
  • Summary:

    The operations in the interface StubContainerInterceptor have an out boolean parameter called "con". It corresponds (I think) to the parameter "proceed_call" described in the text and should therefore be renamed accordingly
  • Reported: QOSCCM 1.0b1 — Thu, 30 Aug 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT

QoS for CCM ComponentInstallation

  • Key: QOSCCM-3
  • Legacy Issue Number: 11319
  • Status: open  
  • Source: THALES ( Olivier Hachet)
  • Summary:

    In section 8.11.4 (deployment), the ComponentInstallation interface is
    referenced. It no more part of the current CCM specification and shall be
    replaced by elements of D&C spec. NodeManager for the physical
    transportation and NodeApplicationManager for the loading of libraries
  • Reported: QOSCCM 1.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:54 GMT