Issue 3742: resolution order (resolution to issue 3642) (interceptors-rtf)
Source: IONA (Mr. Matthew Newhook, )
Nature: Uncategorized Issue
Severity: 
Summary:   My suggested resolution is to change the resolution order to:

The default order for processing a call to
CORBA::ORB::resolve_initial_references for a given <ObjectID> is:
1. Resolve with -ORBInitRef for this <ObjectID> if possible
2. Resolve with a register_initial_reference entry if possible
3. Resolve with pre-configured ORB settings.
4. Resolve with an -ORBDefaultInitRef entry if possible

Note that as Paul said in a later e-mail that this doesn't tell the whole
story because the application programmer should ultimately have control
over this stuff -- and be able to force the application to override
command line ORBInitRef arguments. Therefore a second possible order
could be:

1. Resolve with a register_initial_reference entry if possible
2. Resolve with -ORBInitRef for this <ObjectID> if possible
3. Resolve with pre-configured ORB settings.
4. Resolve with an -ORBDefaultInitRef entry if possible

Resolution: Vote for A, B or NO CHANGE.
Revised Text: Incorporate change close issue. Note that this supercedes issue 3642. Note that choice B passed.
Actions taken:
July 12, 2000: received issue
October 17, 2000: Incorporate change close issue. Note that this supercedes issu
January 9, 2001: closed issue
Discussion: 

End of Annotations:=====
Date: Wed, 12 Jul 2000 13:41:56 -0230
From: Matthew Newhook <matthew@ooc.com>
To: issues@omg.org
Cc: interceptors-ftf@omg.org
Subject: [matthew@ooc.com: resolution order (resolution to issue
3642)]
Message-ID: <20000712134156.A20784@ooc.com>
Mime-Version: 1.0
X-Mailer: Mutt 1.0pre3us
Content-Type: text/plain; charset=us-ascii
X-UIDL: @fhd9~g5!!XZI!!-QMe9

Hi,

  Juergen please record this as a new issue.

  Interceptors people:

  My suggested resolution is to change the resolution order to:

The default order for processing a call to
CORBA::ORB::resolve_initial_references for a given <ObjectID> is:
1. Resolve with -ORBInitRef for this <ObjectID> if possible
2. Resolve with a register_initial_reference entry if possible
3. Resolve with pre-configured ORB settings.
4. Resolve with an -ORBDefaultInitRef entry if possible

Note that as Paul said in a later e-mail that this doesn't tell the
whole
story because the application programmer should ultimately have
control
over this stuff -- and be able to force the application to override
command line ORBInitRef arguments. Therefore a second possible order
could be:

1. Resolve with a register_initial_reference entry if possible
2. Resolve with -ORBInitRef for this <ObjectID> if possible
3. Resolve with pre-configured ORB settings.
4. Resolve with an -ORBDefaultInitRef entry if possible

  Regards, Matthew

----- Forwarded message from Matthew Newhook <matthew@ooc.com> -----

Date: Mon, 19 Jun 2000 17:30:09 -0230
From: Matthew Newhook <matthew@ooc.com>
To: issues@omg.org
Cc: interceptors-ftf@omg.org
Subject: resolution order (resolution to issue 3642)
X-Mailer: Mutt 1.0pre3us

Hi,

 The resolution to issue #3642 is as follows:

4.8.4.1 Default Resolution Order

The default order for processing a call to
CORBA::ORB::resolve_initial_references for a given <ObjectID> is:
1. Resolve with -ORBInitRef for this <ObjectID> if possible
2. Resolve with an -ORBDefaultInitRef entry if possible
3. Resolve with a register_initial_reference entry if possible
4. Resolve with pre-configured ORB settings.


This resolution makes no sense. The -ORBDefaultInitRef parameter
cannot
override register_initial_reference and pre-configured settings since
it
is a default parameter in itself.

The way in which -ORBDefaultInitRef works is that the initial
reference
is constructed using the partial URL style IOR. So if the default init
ref is:

  corbaloc::myhost.com:10000

and the initial reference object-id is "foo" then the created initial
reference for "foo" would be

  corbaloc::myhost.com:10000/foo

Since this mechanism is aimed at creating "default" or fallback
initial
references it must be the last fallback in any resolution order.

Consider, for instance, the OTS which will need to register an OTS
Current. Since this is a local reference the OTS implementation will
need to register an initial reference using
register_initial_reference.
In addition, assume that the user specified a default initial
reference
as above (corbaloc::myhost.com:10000).

The order as defined in the resolution says that the initial reference
for OTSCurrent is

  corbaloc::myhost.com:10000/OTSCurrent

Which is clearly wrong.

Regards, Matthew
-- 
Matthew Newhook                         E-Mail: mailto:matthew@ooc.com
Software Designer                       WWW:    http://www.ooc.com
Object Oriented Concepts, Inc.          Phone:  (709) 738-3725

----- End forwarded message -----

-- 
Matthew Newhook                         E-Mail: mailto:matthew@ooc.com
Software Designer                       WWW:    http://www.ooc.com
Object Oriented Concepts, Inc.          Phone:  (709) 738-3725