CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.7+)

NonStop CORBA Service IDL-generated files are incorporated into the C++ ORB SRL (nsdsrl).

Previously, applications were required to link with the service's archive file to use the service

components. This link is no longer required. For example, if your C++ ORB application uses the

Naming Service, the make step to build the executable was required to include the clause:

-l$(NSD_ROOT)/lib/libnaming.a and/or

-l$(NSD_ROOT)/lib/libeventservice.a

These clauses must be removed because libnaming.a and libeventservice.a are no

longer shipped.

Moving from NonStop JORB to NonStop CORBA

2.3 Update 3 (Java applications)

The ORB now supports the portable bindings specified in OMG specification formal 99-07-53. Java

applications must:

Change any build steps that compiled POA_<interface> to <interface>POA1.

Remove any reference to _<interface>ServantRef from any of your build steps. This file

is no longer generated.

Change all object implementation to extend <interface>POA to POA_<interface>.3.

Remove the cast to org.omg.PortableServer.Servant in calls to the method:

byte[] org.omg.PortableServer.POA.activate_object

(org.omg.PortableServer.Servant servant)

The cast is no longer necessary.

Previously, the application could call the method:

String org.omg.CORBA.ORB.Object_to_string

(org.omg.CORBA.Object object)

with an object implementation. Now the application must first call the method:

org.orm.CORBA Object

org.omg.PortableServer.POA.servant_to_reference(

org.omg.PortableServer.Servant servant)

to get a CORBA object reference, which may then be passed to

org.omg.CORBA.ORB.object_to_string

If an application implemented:

com.tandem.nsdom.PortableServer.ServantExtension

then the method: