CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.3+)

Language Bindings
NSDIDL supports OMG standard C++ and Java language bindings, as defined in the OMG binding
specifications.
Portable Object Adapter
The NonStop CORBA Portable Object Adapter (POA) supports the function defined in the CORBA
portability specification. An Object Adapter is the primary way that an object implementation accesses
the services an ORB provides.
The NonStop CORBA POA:
Allows for development of portable object solutions●
Provides for objects that persist over long periods of time●
Allows a servant to manage multiple objects as one logical object (A servant is a user-defined
object that provides an implementation of the methods of an interface.)
●
Allows multiple distinct instances of a POA to exist in a server●
Supports transient objects●
Supports application use of static and/or dynamic skeletons●
Provides an extensible method for associating policies with objects●
Supports threaded objects●
Application programmers upgrading from the Basic Object Adapter (BOA) to the POA can rethink
design issues because they will probably need to alter their application interfaces to make use of the
POA. However, basic BOA usage can easily be mapped to basic POA usage.
Object Method Invocation
NonStop CORBA supports the Static Invocation Interface (SII).
Naming Service and Interoperable Naming Service
The Naming Service provides for the binding of human-readable object names to NonStop CORBA
objects, and the resolving of these named objects in client requests. NonStop CORBA Naming Service
strictly adheres to the CORBA 2.3 specification. The Naming Service database in NonStop CORBA is
implemented as a structured Enscribe file.
NonStop CORBA also implements the interoperable extension of the Naming Service, allowing users to
access an object through a human-readable URL name. This format makes handling objects simpler for
the user. In addition, the client no longer must import an IOR URL from the server to invoke methods on
that server. The Interoperable Naming Service defines four additions to the Naming Service: