際際滷

際際滷Share a Scribd company logo

First CCM5 presentation

Remedy IT
Remedy IT

The document discusses migrating the Common Component Model (CCM) from being tied to CORBA to a new Open Common Component Architecture Model (OCCAM). It notes that CCM event support is inflexible and requires container support. The proposal is to move event support to a connector and make CORBA optional through a connector. It also discusses providing extensibility to CCM through plugins and QoS4CCM extensions for the lifecycle. The goal is to decouple CCM from CORBA and make it more extensible through plugins and connectors.

1 of 7
Download to read offline
From CORBA Component Model To Common Component Model To ? OMG document mars/2011-03-03 Copyright 息 2011 Page 1
CCM Exists as Component Model for more than a decade Several implementations available Platform and programming language independent But is tied to CORBA in various places Copyright 息 2011 Page 2
Built-in event support CCM has built-in support for events Not very flexible or extensible Requires container-level support for new event passing mechanisms Currently part of the core CCM specification Mostly not used with CBDDS Proposal to move this to a connector that can be much more powerful than the existing event support Copyright 息 2011 Page 3
Extensibility Past solutions resulted in heavy containers and deployments tools Tight integration between CCM implementation and D&C toolchain Container-level code modifications required for new features Revised approach is to provide interceptor support at various levels Locality (D&C toolchain) Container Component Copyright 息 2011 Page 4
What do we want to ask for? Migrate from CORBA Component Model to OCCAM (Open Common Component Architecture Model) Decouple from CORBA specification Make CORBA ORB an optional middleware bus through a connector Rework event support Extensibility CCM through plugins QoS4CCM extensions for LifeCycle Extensibility D&C through plugins (different RFP) Copyright 息 2011 Page 5
Our goal From CCM To OCCAM Open Common Component Architecture Model Copyright 息 2011 Page 6
Thanks for your attention Johnny Willemsen <jwillemsen@remedy.nl> http://www.remedy.nl Copyright 息 2011 Page 7

More Related Content

First CCM5 presentation

  • 1. From CORBA Component Model To Common Component Model To ? OMG document mars/2011-03-03 Copyright 息 2011 Page 1
  • 2. CCM Exists as Component Model for more than a decade Several implementations available Platform and programming language independent But is tied to CORBA in various places Copyright 息 2011 Page 2
  • 3. Built-in event support CCM has built-in support for events Not very flexible or extensible Requires container-level support for new event passing mechanisms Currently part of the core CCM specification Mostly not used with CBDDS Proposal to move this to a connector that can be much more powerful than the existing event support Copyright 息 2011 Page 3
  • 4. Extensibility Past solutions resulted in heavy containers and deployments tools Tight integration between CCM implementation and D&C toolchain Container-level code modifications required for new features Revised approach is to provide interceptor support at various levels Locality (D&C toolchain) Container Component Copyright 息 2011 Page 4
  • 5. What do we want to ask for? Migrate from CORBA Component Model to OCCAM (Open Common Component Architecture Model) Decouple from CORBA specification Make CORBA ORB an optional middleware bus through a connector Rework event support Extensibility CCM through plugins QoS4CCM extensions for LifeCycle Extensibility D&C through plugins (different RFP) Copyright 息 2011 Page 5
  • 6. Our goal From CCM To OCCAM Open Common Component Architecture Model Copyright 息 2011 Page 6
  • 7. Thanks for your attention Johnny Willemsen <jwillemsen@remedy.nl> http://www.remedy.nl Copyright 息 2011 Page 7