com.inprise.vbroker.CosNamingExt
Interface Cluster
- All Superinterfaces: 
 - ClusterOperations, IDLEntity, Object, java.io.Serializable
 
public interface Cluster
- extends Object, ClusterOperations, IDLEntity
 
Allows a number of object bindings to be associated with a single name. The VisiBroker Naming Service 
    supports this feature. Please see the Developers' Guide for details.
    A Cluster is very similar to a Context. There are certain operations found
    in a Context that are not relevant to a
    Cluster. For example, it doesnt make sense binding a
    context to a Cluster. A Cluster is supposed to contain a set of
    object references, not contexts. However, a Cluster
    interface shares many of the same operations with the Context
    interface, such as bind, rebind, resolve, unbind and
    list operations. This common set of operations pertains to operations
    on a group. The only cluster specific operation is
    select(). Another crucial difference between the two is that a Cluster
    does not support compound name. It only uses a single
    component name. This is because there is no directory
    structure in a Cluster. A Cluster stores its object
    references in a flat structure.
 
| Methods inherited from interface com.inprise.vbroker.CORBA.Object | 
_bind_options, _bind_options, _bind, _boa, _get_client_policy, _get_policy_overrides, _ior_value, _ior, _is_bound, _is_local, _is_persistent, _is_remote, _object_name, _orb, _repository_id, _resolve_reference, _set_policy_overrides, _validate_connection, _vis_is_local, _vis_rebind | 
 
| Methods inherited from interface org.omg.CORBA.Object | 
_create_request, _create_request, _duplicate, _get_domain_managers, _get_interface_def, _get_policy, _hash, _is_a, _is_equivalent, _non_existent, _release, _request, _set_policy_override | 
 
 
                 Read the latest documentation online