Issue 551:  Object::is_a (orb_revision)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: Some ORBs are sloppy about existence. One ORB used raises INV_OBJREV whenever object doesn"t exist, even when server can be reached. Behavior is compliant..tighten spec here.

Resolution:   close no change in 2.4
Revised Text: 
Actions taken:
April 22, 1997: received issue
February 23, 1999: moved to orb_revision
Discussion: 

End of Annotations:=====
Return-Path: <daemon>
X-Authentication-Warning: foxtail.dstc.edu.au: michi owned process doing -bs
Date: Tue, 22 Apr 1997 08:25:13 +1000 (EST)
From: Michi Henning <michi@dstc.edu.au>
cc: orbos@omg.org, issues@omg.org
Subject: Re: Object::is_a
Errors-To: owner-issues
Sender: owner-issues
X-OMG: issues
To: issues

> 
> p.s. Clearly, for non_existent there's away to get an authoritative
>     answer:  send an invocation to the object and see if the exception
>     coming back is OBJECT_NOT_EXIST.

I don't think this is reliable - OBJECT_NOT_EXIST is an authoritative
answer, but the ORB may not be able to give that authoritative answer,
for example because the server cannot be reached. In that case, it
would return TRANSIENT.

However, some ORBs are pretty sloppy about existence anyway. For example,
one ORB I've used raises INV_OBJREF whenever an object doesn't exist,
even when the server *can* be reached.

The way I understand it, this behaviour is actually compliant - it may
be a good idea to tighten the spec here. The ORB should be obliged to
raises either TRANSIENT or OBJECT_NOT_EXIST, depending on whether it
can make the decision. INV_OBJREF should be raised only for malformed
references?

							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