Orbix2.3MT interoperability with OmniNames

[Chris Fegan]

Eoin,

My project has been using OmniNames 2.2.0, OrbixWeb3.0, OrbixC++2.2c01
quite successfully for a number of months. We have now run into the
2.2c01 bug with Any types and have had to move to Orbix2.3MT.

At the bottom of you interoperability with Orbix2.3 post you mentioned
that the 2.1 fixes only work in a limited number of circumstances. Could
you please explain the circumstances.

Our experience so far has been:
After applying your suggested 2.1 fixes we could string_to_object and narrow
successfully the IOR string for omniNames root context. If a sub-context
exists trying to resolve that sub-context would end with an exception being 
thrown in decoding of the return value. If a sub-context did not exist trying 
to bind_new_context would also throw trying to decode the return value.

Trying to use the omniNames 2.4.0 (org.omg prefix) and the initial string_to_object
failed.

Is this consistant with your observations?

Thanks, Chris

--

Chris Fegan
Lucent Technologies (AusLabs)
Sydney, Australia