調べもの：仕様書Lightweight CORBA Component Modelの構成 [OCUP&OCRES]
第三版：2009-07-27 21:29
第二版：2009-07-26 11:54:52
初出：2008-03-08 15:16:49
OCRESの学習中。
"The architecture and specifications described in this manual are aimed at software designers and developers who want to produce applications that comply with OMG standards for the Object Request Broker (ORB). The benefit of compliance is, in general, to be able to produce interoperable applications that are based on distributed, interoperating objects."
10. Lightweight CCM Profile
This Lightweight CCM profile is a conformance point based on the extended model as
defined in Section 1.12, “Conformance Requirements,” on page 1-53
10.1 Summary
• Persistence (only session and service components are supported)
• Introspection
• Navigation
• Redundancies, preferring generic over specific.
• Segmentation (not allowed for session or service components)
• Transactions
• Security
• Configurators
• Proxy homes
• Home finders
• CIDL
• POA related mandates
BAD_OPERATION or
NO_IMPLEMENT
IS_LIGHTWEIGHT_COMPONENT
10.2 Changes associated with excluding support for persistence
10.3 Changes associated with excluding support for introspection,
10.4 Changes associated with excluding support for segmentation
10.5 Changes associated with excluding support for transactions
10.6 Changes associated with excluding support for security
10.7 Changes associated with excluding support for configurators
10.8 Changes associated with excluding support for proxy homes
10.9 Changes associated with excluding support for home finders
10.10 Changes adding additional restrictions to the extended model notrepresented by exclusions above.
1.12 Conformance Requirements
この章で該当するのは”8. The Lightweight CCM profile is ..."の下りですね。
3 CCM Implementation Framework
3.1 Introduction
3.2 Component Implementation Framework (CIF) Architecture
3.2.1 Component Implementation Definition Language (CIDL
3.2.2 Component persistence and behavior
3.2.3 Implementing a CORBA Component
3.2.4 Behavioral elements: Executors
3.2.5 Unit of implementation : Composition
3.2.6 Composition structure
3.2.7 Compositions with Managed Storage
3.2.8 Relationship between Home Executor and Abstract Storage Home
3.2.9 Executor Definition
3.2.10 Proxy Homes
3.2.11 Component Object References
3.3 Language Mapping
3.3.1 Overview
3.3.2 Common Interfaces
3.3.3 Mapping Rules
4 The Container Programming Model
4.1 Introduction
4.1.1 External API Types
4.1.2 Container API Type
4.1.3 CORBA Usage Model
4.1.4 Component Categories
4.2 The Server Programming Environment
4.2.1 Component Containers
4.2.2 CORBA Usage Model
4.2.3 Component Factories
4.2.4 Component Activation
4.2.5 Servant Lifetime Management
4.2.6 Transactions
4.2.7 Security
4.2.8 Events
4.2.9 Persistence
4.2.10 Application Operation Invocation
4.2.11 Component Implementations
4.2.12 Component Levels
4.2.13 Component Categories
4.3 Server Programming Interfaces - Basic Components
4.3.1 Component Interfaces
4.3.2 Interfaces Common to both Container API Types
4.3.3 Interfaces Supported by the Session Container API Type
4.3.4 Interfaces Supported by the Entity Container API Type
4.4 Server Programming Interfaces - Extended Components
4.4.1 Interfaces Common to both Container API Types
4.4.2 Interfaces Supported by the Session Container API Type
4.4.3 Interfaces Supported by the Entity Container API Type
4.5 The Client Programming Model
4.5.1 Component-aware Clients
4.5.2 Component-unaware Clients
第二版：2009-07-26 11:54:52
初出：2008-03-08 15:16:49
OCRESの学習中。
"The architecture and specifications described in this manual are aimed at software designers and developers who want to produce applications that comply with OMG standards for the Object Request Broker (ORB). The benefit of compliance is, in general, to be able to produce interoperable applications that are based on distributed, interoperating objects."
10. Lightweight CCM Profile
This Lightweight CCM profile is a conformance point based on the extended model as
defined in Section 1.12, “Conformance Requirements,” on page 1-53
10.1 Summary
• Persistence (only session and service components are supported)
• Introspection
• Navigation
• Redundancies, preferring generic over specific.
• Segmentation (not allowed for session or service components)
• Transactions
• Security
• Configurators
• Proxy homes
• Home finders
• CIDL
• POA related mandates
BAD_OPERATION or
NO_IMPLEMENT
IS_LIGHTWEIGHT_COMPONENT
10.2 Changes associated with excluding support for persistence
10.3 Changes associated with excluding support for introspection,
10.4 Changes associated with excluding support for segmentation
10.5 Changes associated with excluding support for transactions
10.6 Changes associated with excluding support for security
10.7 Changes associated with excluding support for configurators
10.8 Changes associated with excluding support for proxy homes
10.9 Changes associated with excluding support for home finders
10.10 Changes adding additional restrictions to the extended model notrepresented by exclusions above.
1.12 Conformance Requirements
この章で該当するのは”8. The Lightweight CCM profile is ..."の下りですね。
3 CCM Implementation Framework
3.1 Introduction
3.2 Component Implementation Framework (CIF) Architecture
3.2.1 Component Implementation Definition Language (CIDL
3.2.2 Component persistence and behavior
3.2.3 Implementing a CORBA Component
3.2.4 Behavioral elements: Executors
3.2.5 Unit of implementation : Composition
3.2.6 Composition structure
3.2.7 Compositions with Managed Storage
3.2.8 Relationship between Home Executor and Abstract Storage Home
3.2.9 Executor Definition
3.2.10 Proxy Homes
3.2.11 Component Object References
3.3 Language Mapping
3.3.1 Overview
3.3.2 Common Interfaces
3.3.3 Mapping Rules
4 The Container Programming Model
4.1 Introduction
4.1.1 External API Types
4.1.2 Container API Type
4.1.3 CORBA Usage Model
4.1.4 Component Categories
4.2 The Server Programming Environment
4.2.1 Component Containers
4.2.2 CORBA Usage Model
4.2.3 Component Factories
4.2.4 Component Activation
4.2.5 Servant Lifetime Management
4.2.6 Transactions
4.2.7 Security
4.2.8 Events
4.2.9 Persistence
4.2.10 Application Operation Invocation
4.2.11 Component Implementations
4.2.12 Component Levels
4.2.13 Component Categories
4.3 Server Programming Interfaces - Basic Components
4.3.1 Component Interfaces
4.3.2 Interfaces Common to both Container API Types
4.3.3 Interfaces Supported by the Session Container API Type
4.3.4 Interfaces Supported by the Entity Container API Type
4.4 Server Programming Interfaces - Extended Components
4.4.1 Interfaces Common to both Container API Types
4.4.2 Interfaces Supported by the Session Container API Type
4.4.3 Interfaces Supported by the Entity Container API Type
4.5 The Client Programming Model
4.5.1 Component-aware Clients
4.5.2 Component-unaware Clients
タグ：OCRES
コメント 0