Chapter 14: Creating CORBA C++ Components

Limitations

Because external components execute in a different process than the host server, they cannot use the following features:

Sharing, Concurrency, or Bind Thread properties The Sharing, Concurrency, and Bind Thread component properties have no effect when components execute externally, because each component instance runs in a separate process. You can get a form of instance reuse by enabling the Pooling property. With Pooling enabled, the server reuses component processes for multiple invocations.
Transactions or connection caches Server managed transactions and connection caching are not supported in components that execute externally.
C and C++ API routines None of the Jag* C routines or server-side C++ classes documented in Chapter 5, “C Routines Reference,” in the EAServer API Reference are available to components that execute externally. These routines and classes can only be called by code that executes within the host server process.

Input, output, and logging You cannot read from standard input in C++ components (whether they execute in-process or in an external process). C++ components that execute externally cannot call the JagLog C routine, but any text written to standard output is recorded in the server log file.
Stateful components Components that execute externally must be stateless, and no control interface methods are called on the component implementation class. The Auto Demarcation/Deactivation property must be enabled for components that execute externally.