-
Key: NAM-2
-
Legacy Issue Number: 3360
-
Status: open
-
Source: Anonymous
-
Summary:
The latest INS doc 99-12-03.pdf explains the order the Initial reference
should be resolved is
1. Try using -ORBInitDef definition
2. Try using -ORBDefaultInitDef defintion
3. Then finally try with Pre-Configured ORB Settings.The above would be the resolve_initial_references protocol. Now, If the user
sets a -ORBInitDef in the format-ORBInitDef NotificationService=corbaloc:rir:/NotificationService
If the user does orb.resolve_initial_references( "NotificationService" )
then according to the spec, r_i_r() first checks -ORBInitDef's, In this case
finds one and also finds that the NotificationService can be obtained by
r_i_r()
again it calls the same method. Doesn't this lead to an infinite loop ? -
Reported: NAM 1.0 — Thu, 24 Feb 2000 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:58 GMT
NAM — INS Issue: Orderof how the Initial reference is resolved
- Key: NAM-2
- OMG Task Force: Naming FTF