OB::IIOP::Equivalent does not seem to work correctly with 2 equivalent nameservice references

Hi altogether.

I have a question concerning OB422 (on Windows) and the method

Boolean OB::IIOP::Equivalent(const OCI::IOR& ior1, const OCI::IOR& ior2)

(referred to by the class 'Object').


In this method considerable action is taken to evaluate equivalence of two object references and in general this really seems to work. Now I used code for some years which tested the equivalence of multiple root naming contexts prior to registering an IOR in them which worked well within OB404 and in most cases for OB422, too. 

But now I found in OB422 that a root naming context reference received via resolve_initial_references from a registry entry referring 'corbaloc::localhost:10001/NameService' and another root naming context reference retrieved via string_to_object('corbaloc::myhostname:10001/NameService') [and appropriate narrowing] are not found to be equivalent though the localhost is the machine referred by 'myhostname'.

Is there an issue known within this context ? Or was the implementation changed due to the fact that _is_equivalent does not need to true if 2 references denote the same object ?

(Additionally I like to mention that we have changed from concurrency model 'thread_pool' to 'leader_follower' lately but I suspect this is of no relevance within this context.)

Regards
Frank Gierschner
Development


REALTECH

REALTECH system consulting GmbH
Industriestraße 39c
69190 Walldorf
Germany

Tel.: +49.6227.837.306
Fax: +49.6227.837.291 / 9306
mailto:[email protected]
http://www.realtech.com

_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html