Asynchronous Method Invocation for CCM Avatar
  1. OMG Specification

Asynchronous Method Invocation for CCM — Closed Issues

  • Acronym: AMI4CCM
  • Issues Count: 1
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
AAR-1 Remove AMI4CCM_Base connector AMI4CCM 1.0 AMI4CCM 1.1 Resolved closed

Issues Descriptions

Remove AMI4CCM_Base connector

  • Key: AAR-1
  • Status: closed  
  • Source: Remedy IT ( Johnny Willemsen)
  • Summary:

    We propose to remove the AMI4CCM_Base connector completely from the AMI4CCM specification. Each AMI4CCM connector is already identified by the fact that it is a template instantation of the AMI4CCM_Connector as part of the CCM_AMI::Connector_T templated module. There is nothing that is shared between all AMI4CCM connectors, there are no attributes or operations defined. This base connector only leads to increased code generation and complexity. It is also something the user doesn't see.

  • Reported: AMI4CCM 1.0 — Thu, 21 Aug 2014 19:34 GMT
  • Disposition: Resolved — AMI4CCM 1.1
  • Disposition Summary:

    Remove AMI4CCM_Base connector

    The AMI4CCM_Base connector was added in the original spec but doesn't add any value, it only adds footprint and complexity. The reason of the base is not documented at all, it is just there. As far as we could tell this was initially added to make the implementation easier, but at the end we just identified the specific templated module instantiation of CCM_AMI::AMI4CCM_Connector

  • Updated: Wed, 8 Jul 2015 11:39 GMT
  • Attachments: