Pseudocomponents must be implemented in C++ or Java. If using Java, the component type must be Java/CORBA; you cannot instantiate an Enterprise JavaBean as a pseudocomponent.
Since pseudocomponents execute outside of the EAServer dispatcher, their execution is not governed by component properties defined in EAServer Manager. Thus, components that run as pseudocomponents are subject to these restrictions:
They cannot participate in server-managed transactions.
Lifecycle interface methods, such as those in CtsComponents::ObjectControl, are not called and instances are never pooled or reused. Each time a client program instantiates a proxy instance of a pseudocomponent, a new instance of the implementation class is constructed.
They are not affected by component threading properties. A pseudocomponent’s methods run in the same process of the calling program, on the same thread from which they are called.
Pseudocomponents executed in standalone programs cannot use server-side classes and methods such as connection management, client credential access, and so forth. These classes and methods are available only to components executed by the EAServer component dispatcher. A pseudocomponent that is executed by a server-dispatched component can use server-side features, but does so in the context of the server-dispatched component that instantiated the pseudocomponent.
They are not affected by access control restraints. Any client with local access to a component’s implementation library or class can instantiate the component as a pseudocomponent.
