Using the Naming Service


The Naming Service is the CORBA service which allows to manage objects in a hierarchical named trees which looks like directory trees. Storing object references in the Naming Service provides a very easy way to make it accessible to clients and services. The root context of any Naming Service can be stored inside each Naming Service under a name common to all Naming Services, so that the path to any object reference is the same whichever Naming Service is used.

The whole OMG IDL specification of the Naming Service is implemented, including the interface NamingContextExt, as it is defined in the OMG document Naming_00-11-01.

The Naming Service is an initial service which runs inside the OrbRiver orb, its object id is "NameService".


No limitation is known for this service.


The Naming Service objects persistent state is saved in the file $ORBRIVER_DIR/etc/Naming_<Id> where <Id> is the ORB identity of the orb containing this Naming Service. This file is only updated when the orb is cleanly stopped (see Stopping OrbRiver with stop_orb).

Editing with name_editor

name_editor is the tool to edit the Naming Service of a given running orb. This means:

Its switches are the orb connection switches (see Client and Service switches).

name_editor prompts for commands. The prompt is "-> ". Several commands execute actions on the bindings which can be named by their absolute name or a name relative to the current context. At startup, the current context is the root context of the Naming Service (named by a single separator).
Names are build with component names separated by a (configurable) separator.
The modifications done with name_editor are permanent (reloaded automatically when the orb starts) if the orb has been stopped by "stop_orb".

The commands are not case sensitive and some have a short alias.
The possible commands are:

Email Micro Focus support

Copyright Micro Focus 2002-2014. All rights reserved.