CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.3+)

Interface Repository Daemon) are placed in $NSD_Root/urls by default. NonStop DOM 2.0
servers placed these IORs in $NSD_ROOT/etc. The file names have also changed:
NonStop DOM 2.0 NonStop CORBA 2.3
etc/root_nc.ior urls/NameService
etc/es.ior urls/EventService
etc/tm.ior urls/Transaction Factory
etc/ir/ior urls/InterfaceRepository
Moving from NonStop DOM to NonStop CORBA 2.3
Update 3 (C++ Applications)
The ORB no longer supports the environment parameter form of APIs. Applications that were
coded to use the environment parameter in ORB APIs must be re-coded to use C++ exceptions. If
you use the macros in trycatch.h, you need only recompile.
1.
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.
2.
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.
2.
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.
4.