Joint Client/Servers

e-docs > Tuxedo > Administering a Tuxedo Application at Run Time > Joint Client/Servers

Administering a Tuxedo Application at Run Time

start_persistent_systemid

Synopsis

Activates an object, sets the ORB and the POA to the proper state, sets the output parameter stroid, and returns an object reference to the activated object.

IDL

Object start_persistent_systemid( 
                      in PortableServer::Servant      servant, 
                      in CORBA::RepositoryId          rep_id,
                      out string                      stroid) 
    raises ( ServantAlreadyActive );

C++ Binding

CORBA::Object_ptr start_persistent_systemid(
                       PortableServer::Servant          servant,
                       const char*                      rep_id,
                       char*&                            stroid);

Java Binding

org.omg.CORBA.Object start_persistent_systemid( 
                       org.omg.PortableServer.Servant   servant,
                       java.lang.String                 rep_id,
                       java.lang.String                 stroid);

Arguments

servant

An instance of the C++ implementation class for the interface.

rep_id

The repository ID of the interface.

stroid

This argument is set by the system and is opaque to the user. The client will use it when it reactivates the object at a later time (using restart_persistent_systemid), most likely after the client process has terminated and restarted.

Exceptions

ServantAlreadyActive

The servant is already being used for a callback. A servant can be used only for a callback with a single ObjectId. To receive callbacks on objects containing different ObjectIds, you must create different servants and activate them separately. The same servant can be reused only if a stop operation tells the system to stop using the servant for its original ObjectId.

CORBA::BAD_PARAMETER

The repository ID was a NULL string or the servant was a NULL pointer.