2005Unpublished venueRequires access

CORBA Components

Andy Ju An Wang, Kai Qian

Open publisher page 0 citations

Abstract

CORBA stands for Common Object Request Broker Architecture, which is an open, vendor-independent architecture and component infrastructure for computer applications working in a networking or distributed environment. Using the standard protocol IIOP and ORB, a CORBA component is both vendor neutral and platform independent, which means a CORBA component from any vendor can work well with other CORBA components from other vendors on any computers or operating systems, regardless of what programming languages have been used to implement those CORBA components. CORBA Component Model (CCM) is an open standard introduced in CORBA 3.x for component based software development. CCM has significantly reduced the software complexity, making it easier to adapt, maintain, extend, or aggregate software components. A CCM component interface exposes all its ports. It has facets, receptacles, event sources, event sinks, and configurable attributes. It is easy to connect multiple CCM components by their ports. CCM also provides a standard facility to support component packaging, assembling, and deployment. This chapter discusses how to design, implement, package, deploy, execute, and reuse CCM components. OpenCCM is used as a reference implementation of CCM in our discussion.

About this research paper

What this paper is about

CORBA stands for Common Object Request Broker Architecture, which is an open, vendor-independent architecture and component infrastructure for computer applications working in a networking or distributed environment. Using the standard protocol IIOP and ORB, a CORBA component is both vendor neutral and platform independent, which means a CORBA component from any vendor can work well with other CORBA components from other vendors on any computers or operating systems, regardless of what programming languages have been used to implement those CORBA components. CORBA Component Model (CCM) is an open standard introduced in CORBA 3.x for component based software development. CCM has significantly reduced the software complexity, making it easier to adapt, maintain, extend, or aggregate software components. A CCM component interface exposes all its ports. It has facets, receptacles, event sources, event sinks, and configurable attributes. It is easy to connect multiple CCM components by their ports. CCM also provides a standard facility to support component packaging, assembling, and deployment. This chapter discusses how to design, implement, package, deploy, execute, and reuse CCM components. OpenCCM is used as a reference implementation of CCM in our discussion.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

CORBA stands for Common Object Request Broker Architecture, which is an open, vendor-independent architecture and component infrastructure for computer applications working in a networking or distributed environment. Using the standard protocol IIOP and ORB, a CORBA component is both vendor neutral and platform independent, which means a CORBA component from any vendor can work well with other CORBA components from other vendors on any computers or operating systems, regardless of what programming languages have been used to implement those CORBA components. CORBA Component Model (CCM) is an open standard introduced in CORBA 3.x for component based software development. CCM has significantly reduced the software complexity, making it easier to adapt, maintain, extend, or aggregate software components. A CCM component interface exposes all its ports. It has facets, receptacles, event sources, event sinks, and configurable attributes. It is easy to connect multiple CCM components by their ports. CCM also provides a standard facility to support component packaging, assembling, and deployment. This chapter discusses how to design, implement, package, deploy, execute, and reuse CCM components. OpenCCM is used as a reference implementation of CCM in our discussion.

Key concepts: Common Object Request Broker Architecture, Computer science, Component (thermodynamics), Component-based software engineering, Operating system, Reuse, Vendor, Common Component Architecture

Related papers

Back to paper searchBrowse research topicsOriginal source
CORBA Components — Research Paper | ScholarLens