[omniORB] Bug? with NameService and Windows-registry

[Martin Trappel]

Hello,
I have percieved that the behavior of omniORB is slightly different if the
NameService is supplied via the Windows-Registry instead of with the
commandline-argument -ORBInitRef ...

* When supplied via the Registry, list_initial_services() does only list the
NameService  a f t e r  I did resolve_initial_references("NameService").
When I use the commandline, the NameService is always listed by list_...

* Also, when I supply the NS via the Registry, and then try to
resolve_initial_references("MyService"); where MyService does not exist and is not
supplied via -ORBInitRef, resolve_initial_references will block forever.
After that, resolve_initial_references(<Anything>) will hang in any program
that does not get the NameService directly via the commandline, until I
restart the NameService.
My System: WinNT 4.0 sp6, MSVC5 sp3

Since I do not use the registry anymore (we have our own ini-Files in the
System where I use omniORB), this is no problem for me, but I thought I might
point this out, if anyone has similar problems.

best regards,
Martin 

-- 
------------------------------
/\  tm5@gmx.at
\/  Trappel Martin
------------------------------
DSS/DH PGP-Key ID: 0xBF60E83E
------------------------------

GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net