java.lang.Objectorg.omg.CORBA.ORB
Direct Known Subclasses:
ORB, ORB, ORBSingleton, PIORB, ORB, ORB, ORBSingleton, POAORB, ORBImpl
ORB class also provides
"pluggable ORB implementation" APIs that allow another vendor's ORB
implementation to be used.
An ORB makes it possible for CORBA objects to communicate with each other by connecting objects making requests (clients) with objects servicing requests (servers).
The ORB class, which
encapsulates generic CORBA functionality, does the following:
(Note that items 5 and 6, which include most of the methods in
the class ORB, are typically used with the Dynamic Invocation
Interface (DII) and the Dynamic Skeleton Interface
(DSI).
These interfaces may be used by a developer directly, but
most commonly they are used by the ORB internally and are
not seen by the general programmer.)
resolve_initial_references
TypeCode
Any
NamedValue
Context
Environment
NVList) containing these objects
The ORB class can be used to obtain references to objects
implemented anywhere on the network.
An application or applet gains access to the CORBA environment
by initializing itself into an ORB using one of
three init methods. Two of the three methods use the properties
(associations of a name with a value) shown in the
table below.
| Property Name | Property Value |
|---|---|
| org.omg.CORBA.ORBClass | class name of an ORB implementation |
| org.omg.CORBA.ORBSingletonClass | class name of the ORB returned by init() |
These properties allow a different vendor's ORB
implementation to be "plugged in."
When an ORB instance is being created, the class name of the ORB implementation is located using the following standard search order:
Note that Java IDL provides a default implementation for the
fully-functional ORB and for the Singleton ORB. When the method
init is given no parameters, the default Singleton
ORB is returned. When the method init is given parameters
but no ORB class is specified, the Java IDL ORB implementation
is returned.
The following code fragment creates an ORB object
initialized with the default ORB Singleton.
This ORB has a
restricted implementation to prevent malicious applets from doing
anything beyond creating typecodes.
It is called a singleton
because there is only one instance for an entire virtual machine.
ORB orb = ORB.init();
The following code fragment creates an ORB object
for an application. The parameter args
represents the arguments supplied to the application's main
method. Since the property specifies the ORB class to be
"SomeORBImplementation", the new ORB will be initialized with
that ORB implementation. If p had been null,
and the arguments had not specified an ORB class,
the new ORB would have been
initialized with the default Java IDL implementation.
Properties p = new Properties();
p.put("org.omg.CORBA.ORBClass", "SomeORBImplementation");
ORB orb = ORB.init(args, p);
The following code fragment creates an ORB object
for the applet supplied as the first parameter. If the given
applet does not specify an ORB class, the new ORB will be
initialized with the default Java IDL implementation.
ORB orb = ORB.init(myApplet, null);
An application or applet can be initialized in one or more ORBs. ORB initialization is a bootstrap call into the CORBA world.
JDK1.2 - | Methods from java.lang.Object: |
|---|
| equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from org.omg.CORBA.ORB Detail: |
|---|
ImplBase class corresponding to the interface that is
supported by the server. The servant must thus be a CORBA object
reference, and inherit from org.omg.CORBA.Object.
Servants created by the user can start receiving remote invocations
after the method connect has been called. A servant may also be
automatically and implicitly connected to the ORB if it is passed as
an IDL parameter in an IDL method invocation on a non-local object,
that is, if the servant object has to be marshalled and sent outside of the
process address space.
Calling the method Deprecated by the OMG in favor of the Portable Object Adapter APIs. |
TypeCode object for an IDL abstract interface. |
TypeCode object representing an IDL alias
(typedef).
The TypeCode object is initialized with the given id,
name, and original type. |
Any object initialized to
contain a Typecode object whose kind field
is set to TCKind.tc_null. |
TypeCode object representing an IDL array.
The TypeCode object is initialized with the given length and
element type. |
Deprecated! Use - the new DynAnyFactory API instead
DynAny object from the given
TypeCode object.
|
ContextList object. |
Deprecated! Use - the new DynAnyFactory API instead
DynAny object from the given
Any object.
|
Deprecated! Use - the new DynAnyFactory API instead
DynArray object from the given
TypeCode object.
|
Deprecated! Use - the new DynAnyFactory API instead
DynEnum object from the given
TypeCode object.
|
Deprecated! Use - the new DynAnyFactory API instead
DynSequence object from the given
TypeCode object.
|
Deprecated! Use - the new DynAnyFactory API instead
DynStruct object from the given
TypeCode object.
|
Deprecated! Use - the new DynAnyFactory API instead
DynUnion object from the given
TypeCode object.
|
TypeCode object representing an IDL enum.
The TypeCode object is initialized with the given id,
name, and members. |
Environment object. |
ExceptionList object. |
TypeCode object representing an IDL exception.
The TypeCode object is initialized with the given id,
name, and members. |
TypeCode object for an IDL fixed type. |
TypeCode object representing an IDL interface.
The TypeCode object is initialized with the given id
and name. |
NVList with (probably) enough
space for the specified number of NamedValue objects.
Note that the specified size is only a hint to help with
storage allocation and does not imply the maximum size of the list. |
NamedValue object
using the given name, value, and argument mode flags.
A |
TypeCode object for an IDL native type. |
NVList initialized with argument
descriptions for the operation described in the given
OperationDef object. This OperationDef object
is obtained from an Interface Repository. The arguments in the
returned NVList object are in the same order as in the
original IDL operation definition, which makes it possible for the list
to be used in dynamic invocation requests. |
org.omg.CORBA.portable.OutputStream into which
IDL method parameters can be marshalled during method invocation. |
|
TypeCode object representing a
a recursive IDL sequence.
For the IDL
Struct Node {
long value;
Sequence <Node> subnodes;
};
|
TypeCode object which
serves as a placeholder for a concrete TypeCode during the process of creating
TypeCodes which contain recursion. The id parameter specifies the repository id of
the type for which the recursive TypeCode is serving as a placeholder. Once the
recursive TypeCode has been properly embedded in the enclosing TypeCode which
corresponds to the specified repository id, it will function as a normal TypeCode.
Invoking operations on the recursive TypeCode before it has been embedded in the
enclosing TypeCode will result in a BAD_TYPECODE exception.
For example, the following IDL type declaration contains recursion:
Struct Node {
Sequence<Node> subnodes;
};
To create a TypeCode for struct Node, you would invoke the TypeCode creation operations as shown below:
String nodeID = "IDL:Node:1.0";
TypeCode recursiveSeqTC = orb.create_sequence_tc(0, orb.create_recursive_tc(nodeID));
StructMember[] members = { new StructMember("subnodes", recursiveSeqTC, null) };
TypeCode structNodeTC = orb.create_struct_tc(nodeID, "Node", members);
Also note that the following is an illegal IDL type declaration:
Struct Node {
Node next;
};
Recursive types can only appear within sequences which can be empty. That way marshaling problems, when transmitting the struct in an Any, are avoided. |
TypeCode object representing an IDL sequence.
The TypeCode object is initialized with the given bound and
element type. |
TypeCode object representing a bounded IDL
string.
The TypeCode object is initialized with the given bound,
which represents the maximum length of the string. Zero indicates
that the string described by this type code is unbounded. |
TypeCode object representing an IDL struct.
The TypeCode object is initialized with the given id,
name, and members. |
TypeCode object representing an IDL union.
The TypeCode object is initialized with the given id,
name, discriminator type, and members. |
TypeCode object for an IDL value box. |
TypeCode object for an IDL value type.
The concrete_base parameter is the TypeCode for the immediate
concrete valuetype base of the valuetype for which the TypeCode
is being created.
It may be null if the valuetype does not have a concrete base. |
TypeCode object representing a bounded IDL
wstring (wide string).
The TypeCode object is initialized with the given bound,
which represents the maximum length of the wide string. Zero indicates
that the string described by this type code is unbounded. |
OBJECT_NOT_EXIST exception.
Once an ORB has been destroyed, another call to init
with the same ORBid will return a reference to a newly constructed ORB.
If
For maximum portability and to avoid resource leaks, an application should
always call |
org.omg.CORBA.OBJECT_NOT_EXIST back to the
remote client. Thus the object appears to be destroyed from the
point of view of remote clients. Note, however, that local requests issued
using the servant directly do not
pass through the ORB; hence, they will continue to be processed by the
servant.
Calling the method Deprecated by the OMG in favor of the Portable Object Adapter APIs. |
Deprecated! use - resolve_initial_references.
Current object.
The Current interface is used to manage thread-specific
information for use by services such as transactions and security. |
Context object. |
Request instance for which a response
has been received. |
TypeCode object that represents
the given primitive IDL type. |
|
ORB singleton object. This method always returns the
same ORB instance, which is an instance of the class described by the
org.omg.CORBA.ORBSingletonClass system property.
This no-argument version of the method
This method is not intended to be used by applets, and in the event
that it is called in an applet environment, the ORB it returns
is restricted so that it can be used only as a factory for
If an ORB is created using this method from an applet,
a system exception will be thrown if
methods other than those for
creating |
ORB instance for a standalone
application. This method may be called from applications
only and returns a new fully functional ORB object
each time it is called. |
ORB instance for an applet. This
method may be called from applets only and returns a new
fully-functional ORB object each time it is called. |
|
The resulting |
work_pending and perform_work
can be used in
conjunction to implement a simple polling loop that multiplexes
the main thread among the ORB and other activities. |
|
|
shutdown. It may be used by multiple threads which
get all notified when the ORB shuts down. |
|
|
init method to pass in its parameters. |
init method to pass in its parameters. |
If the wait_for_completion parameter
is true, this operation blocks until all ORB processing (including
processing of currently executing requests, object deactivation,
and other object adapter operations) has completed.
If an application does this in a thread that is currently servicing
an invocation, the BAD_INV_ORDER system exception
will be thrown with the OMG minor code 3,
since blocking would result in a deadlock.If the wait_for_completion parameter is FALSE,
then shutdown may not have completed upon return.
While the ORB is in the process of shutting down, the ORB operates as normal,
servicing incoming and outgoing requests until all requests have been completed.
Once an ORB has shutdown, only object reference management operations
may be invoked on the ORB or any object reference obtained from it.
An application may also invoke the
The |
object_to_string
back to a CORBA object reference. |
true if the ORB needs the main thread to
perform some work, and false if the ORB does not
need the main thread. |