Server-Side Mapping |
7 |
It will be patterned after the server framework architecture to be described by the final submission to the Server Side Portability RFP.
Issue - This chapter is subject to revision pending the outcome of the Portability RFP submission
<interface_name>
the mapping defines a Java class as follows:// Java
public class _<interface_name>ImplBase implements <interface_name> {
}
Each object implementation implements ORB objects that supports a most derived IDL interface. If this interface is <interface_name>, then the servant class must extend _<interface_name>ImplBase
.
The servant class must define public methods corresponding to the operations and attributes of the IDL interface supported by the object implementation, as defined by the mapping specification for IDL interfaces. Providing these methods is sufficient to satisfy all abstract methods defined by _<interface_name>ImplBase
.
connect()
method (see Section 6.12, "ORB").
Note that calling connect()
when an object is already connected has no effect.
disconnect()
method (see Section 6.12, "ORB"). After this method returns, incoming requests will be rejected by the ORB by raising the CORBA::OBJECT_NOT_EXIST exception. The effect of this method is to cause the ORB object to appear to be destroyed from the point of view of remote clients.
Note that calling disconnect()
when the object is not connected has no effect.
Note however, that requests issued using the servant directly (e.g. using the implementatioon's this pointer) do not pass through the ORB; these requests will continue to be processed by the servant.
Issue - dependent upon the Portability specification