[omniORB] OmniORB 4.0.2 WinNT version not reading config from registry

[Clarke Brunt]

As the subject says: just tried OmniORB 4.0.2 having been using 4.0.1 on
WinNT with the config settings in the Registry.

Now resolve_initial_references can't find "NameService". I've stepped
through the code, and find that whereas in corbaOrb.cc 4.0.1 had:

#if !defined(NTArchitecture)
    const char* config_fname = CONFIG_DEFAULT_LOCATION;
#else
    const char* config_fname = 0;
#endif
    {
      const char* f = getenv(CONFIG_ENV);
      if (f) config_fname = f;
    }
    if (config_fname) {
      orbOptions::singleton().importFromFile(config_fname);
    }
#if defined(NTArchitecture) && !defined(__ETS_KERNEL__)
    else {
      // Parse configuration from registry on NT if no configuration
      // file is specified.
      orbOptions::singleton().importFromRegistry();
    }
#endif

4.0.2 has:

    const char* config_fname = CONFIG_DEFAULT_LOCATION;
    {
      const char* f = getenv(CONFIG_ENV);
      if (f) config_fname = f;
    }
    if (config_fname) {
      orbOptions::singleton().importFromFile(config_fname);
    }
#if defined(NTArchitecture) && !defined(__ETS_KERNEL__)
    else {
      // Parse configuration from registry on NT if no configuration
      // file is specified.
      orbOptions::singleton().importFromRegistry();
    }
#endif

So 4.0.1 would never read from the default config file (only one specified
in env variable), whereas 4.0.2 has been 'fixed' to use the default config
file, or the one in the env variable, but will _never_ read the registry. Am
I missing something, or are there not many Windows users out there?

--
Clarke Brunt, Principal Software Engineer, Yeoman Navigation