Issue 1156: resolve_initial_references under-specified (orb_revision) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: resolve_initial_references can raise an InvalidName exception. However, the text in section 4.5 does not attach any semantics to that exception (in fact, it does not mention the exception at all). The spec needs to state explicitly *when* InvalidName should be raised. Presumably, the intent was that it would be raised for unknown ObjectIds, such as "XXXX". Resolution: Needs no further action in Core RTF. Close this issue no change. Revised Text: Actions taken: April 17, 1998: received issue June 25, 1998: moved from port-rtf to orb_revision August 19, 1999: closed issue Discussion: This has been addressed in the submission that was accepted in response to the Interoperable Name Service RFP, and hence will be fixed in Core as soon as that adopted spec is incorporated into Core End of Annotations:===== Return-Path: X-Authentication-Warning: tigger.dstc.edu.au: michi owned process doing -bs Date: Sat, 18 Apr 1998 06:29:35 +1000 (EST) From: Michi Henning Reply-To: Michi Henning To: issues@omg.org, port-rtf@omg.org Subject: resolve_initial_references under-specified Hi, resolve_initial_references can raise an InvalidName exception. However, the text in section 4.5 does not attach any semantics to that exception (in fact, it does not mention the exception at all). The spec needs to state explicitly *when* InvalidName should be raised. Presumably, the intent was that it would be raised for unknown ObjectIds, such as "XXXX". Question: What should happen if I call resolve_initial_references with an ObjectId of "NameService" in an ORB that does not offer a name service? Should the exception still be InvalidName? I assume the answer is "yes"? In other words, InvalidName should be raised for any ObjectId not returned by list_initial_services? If that is correct, the spec needs to state this. Another question: What if resolve_initial_references cannot get the reference to some (valid) service for internal reasons? Which exception should be raised? Is any appropriate system exception acceptable? Return value: The spec should explicitly state that resolve_initial_references can *never* return a nil reference. There are currently implementations that do. However, when you think about it, this is totally meaningless. If the call succeeds (does not raise an exception), I should be entitled to expect that I am given a valid reference via which I can access the service. A nil reference most definitely does not fit that description... Cheers, Michi. -- Michi Henning +61 7 33654310 DSTC Pty Ltd +61 7 33654311 (fax) University of Qld 4072 michi@dstc.edu.au AUSTRALIA http://www.dstc.edu.au/BDU/staff/michi-henning.html Return-Path: X-Authentication-Warning: tigger.dstc.edu.au: michi owned process doing -bs Date: Wed, 2 Sep 1998 21:22:17 +1000 (EST) From: Michi Henning To: orb_revision@omg.org Subject: (Non)proposal for 1156 I suggest to defer issue 1156 keeping it open until after the Interoperable Naming Service submission is done. The INS Submission will probably say something about exactly under what circumstances a token passed to resolve_initial_references will cause InvalidName to be raised, and I'd rather not mess with this until after we know we won't have to change it yet again. Cheers, Michi. -- Michi Henning +61 7 33654310 DSTC Pty Ltd +61 7 33654311 (fax) University of Qld 4072 michi@dstc.edu.au AUSTRALIA http://www.dstc.edu.au/BDU/staff/michi-henning.html