2.2 How a CORBA Object Comes into Being

The data that makes up a CORBA object may have its origin as a record in a database. The record in the database is the persistent, or durable, state of the object. This record becomes accessible via a CORBA object in an Oracle Tuxedo domain when the following sequence has occurred:

1. The server application’s factory creates a reference for the object. The object reference includes information about how to locate the record in the database.
2. Using the object reference created by the factory, the client application issues a request on the object.
3. The object is instantiated. The object is instantiated by the TP Framework by invoking the Server::create_servant method, which exists in the Server object.
4. The Oracle Tuxedo domain invokes the activate_object operation on the object, which causes the record containing state to be read into memory.

Whereas a language object exists only within the boundaries of the execution of the application, a CORBA object may exist across processes and machine systems. The Oracle Tuxedo system provides the mechanism for constructing an object and for making that object accessible to the application.

The Oracle Tuxedo CORBA server application programmer is responsible for writing the code that initializes an object’s state and the code that handles that object’s state after the object is no longer active in the application. If the object has data in durable storage, this code includes the operations that read from and write to durable storage. For more information about developing server applications, see Creating CORBA Server Applications in the Oracle Tuxedo online documentation.