CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.7+)

Moving from NonStop CORBA 2.3 Update 1 to

NonStop CORBA 2.3 Update 3 or Later

For Updates 3 through 6,

C++ applications must be recompiled.1.

C++ IDL files must be recompiled by the new IDL compiler.2.

For Java applications, nothing needs to be done.3.

For Update 7,

C++ applications must be recompiled.1.

C++ IDL files must be recompiled by the new IDL compiler.2.

Java IDL files must be recompiled by the new IDL compiler3.

Java source files must be recompiled using NonStop Server for Java version 3.0.4.

Moving Any Application from NonStop DOM or

NonStop JORB to NonStop CORBA 2.3 Update 3

Applications (C++ and Java) must be recompiled1.

IDL files must be recompiled by the new IDL complier.2.

IORs generated by NonStop Servers (Naming Service, Event Service, Transaction Service, and

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.