COFE interfaces and exposed objects

Most of the objects expose CAPE-OPEN interfaces directly. The CAPE-OPEN can be recognized by their naming convention, they all start with ICape. Although this document indicates to some extent which CAPE-OPEN interfaces can be expected to be implemented, for reference of the interfaces the reader is referred to the CAPE-OPEN interface specifications documents, which are available from CO-LaN, the CAPE-OPEN Laboratory Network, and partially included in these documents.

The interfaces that are exposed by COFE all start with ICOFE:

• ICOFEDocument: this interface is exposed by the COFE document object. See Creating a COFE document by automation for how to obtain an object of the COFE document type
• ICOFEStream: this interface is exposed by COFE streams (material-, energy- and information streams)
• ICOFEMaterial: this interface is exposed by COFE material objects

Error handling

All CAPE-OPEN interfaces should implement CAPE-OPEN error handling. For more information, see Error Common Interface from the CAPE-OPEN interface specifications. Specifically, all TEA, CORN, COUSCOUS and COFE objects return ECapeUnknownHR, and a descriptive error text can be obtained through the ECapeUser interface.

COFE may return automation other than CAPE-OPEN errors. Specifically, an error code and error description will be provided. Error codes that can be returned are: