|
|
 Common Interfaces
-
 Error Common Interface (323 KB) - Error Handling defines how to manage execution errors (abnormal terminations). When a request is made, if this request is successful it raises no error, otherwise it raises an error. When an error occurs, the execution is immediately aborted. This Error Handling interface gives a classification and a hierarchy of potential errors occurring in CO compliant components. All CO components must implement it.
Changes in this version:
None, however it has been polished and this interface has been extensively tested.
- Identification Common Interface (246 KB)
- Identification interface provides the means for all CO components to be identified by name and textual description. All CO components must implement it.
Changes in this version:
None however it has been polished, and this interface has been extensively tested.
- Collections (202kB)
- Collections interface defines a standard way of managing collections of things. The aim of the Collection interface is to give a CO component the possibility to expose a list of objects to any client of the component. The client will not be able to modify the collection, i.e. removing, replacing or adding elements. However, since the client will have access to any CO interface exposed by the items of the collection, it will be able to modify the state of any element.
Changes in this version:
Did not exist previously. Need to be thoroughly tested.
- Parameters (345 KB)
- Defines a standard access to component parameters. This specification will be used by CO components wishing to expose some of their internal data to their clients. The interface is made up of two different parts, each corresponding to a different client need: the first part is a fixed, static aspect that describes the Parameter, such as a type, name, description, dimensionality etc. The second part deals with value of the parameter itself. It is expected that the parameter values will change quite frequently both within and outside of the component that needs it.
Changes in this version:
None, but this interface has been extensively tested.
- Utilities (266 KB)
- Gathers a number of useful functionalities that can be requested from process modelling components. In version 1.0, this interface provides the means to set the simulation context, to collect component parameters, to manage lifecycle of components (creation and termination) and to edit, that is, to open an edit GUI for the component.
Changes in this version:
Did not exist previously. Has been thoroughly tested.
- Persistence (235 KB)
- Defines how models and model elements are stored and retrieved. Most simulation environments allow the possibility to store at any moment the state of a simulation case, in order to be able to restore it at any time in the future. In the CAPE-OPEN distributed environment, where different pieces of the simulation may be implemented by different vendors, the Persistence interface proposes a standard mechanism to provide this feature. This interface is different from all others, as it does not define any new method. Instead, it explains how to use standard persistence mechanisms provided by middleware (COM and CORBA) for this purpose.
Changes in this version:
Did not exist previously. Has been thoroughly tested.
 Known Objects (0 byte
)- Known objects gather a large number of standard identifiers used in interfaces, such as Thermo, PPDB, and petroleum fractions. These are lists of properties names, names of methods; identification of phases, etc., which form a consistent set of names used throughout these interfaces.
Changes in this version:
This is ongoing work.
|
|
(c) CO-LaN, 2001-2008. All rights are reserved unless specifically stated otherwise.
| |
