3D PLM Enterprise Architecture |
Middleware Abstraction |
The Middleware Abstraction modeler deals with presenting system capabilities in a simple and single way to the applications, and thus hides the differences of operating systems. It also includes the basics of the Object Modeler, of the ENOVIA Event Model, and of the XML parser.
Middleware | Object Modeler | ENOVIA Event Model | XML Parser | |
![]() |
![]() |
Technical Articles | |
Creating Interfaces | The way to expose you component behavior |
Creating Components | Enabling your clients to create your usable and scalable objects |
Using Components | Creating component instances, asking for interface pointers, calling interface methods, and managing component lifecycle |
Object Modeler Inheritances | Factorizing and reusing your code |
Creating Interfaces for Automation | Making your interfaces available from scripting languages |
Implementing Interfaces for Automation | Making your components available from scripting languages |
The CAA V5 IDL Compiler | Describing the CAA V5 IDL and converting your interfaces to C++ abstract classes |
[Top] | |
Use Cases | |
Creating Interfaces | Declaring component expected type and behavior |
Creating Components | Making objects that implement interfaces |
Creating and Instantiating a Component | Implementing CATICreateInstance and using CATInstantiateComponent |
Instantiating a Component using its CLSID | Implementing IClassFactory and using CATCreateInstance |
Creating a Component Factory | Enabling component instantiation without be tied to the component implementation |
Implementing an Interface Using the BOA | Creating a data extension class that derives from the interface |
Using Components | Creating components, asking for interface pointers, and managing component life cycle |
Using OM-derivation | Factorizing and reusing code |
[Top] | |
Quick Reference | |
System Reference | Interface and class reference for system objects |
AutomationInterfaces Reference | Class reference for scripting utility functions |
Interface Quick Reference | The detailed road map to create your interfaces |
About Globally Unique IDentifiers | Naming your interface with a label unique the world over for some centuries |
What Is HRESULT? | A standard return value for all your interface methods |
About __stdcall | Making your interface methods comply with Automation |
The Execution Context | The way to control where your request can be executed |
[Top] |
Version: 1 [Mar 2000] | Document created |
[Top] |
Copyright © 1994-2005, Dassault Systèmes. All rights reserved.