[omniORB] interoperability between 3.0.4 and 4.0 b2

[Duncan Grisby]

On Tuesday 3 September, Richard Bouska wrote:

> Trying to connect of omninames linked with omniORB3 by client compiled 
> with 4.0 I get following message:
> 
>  From endpoint: giop:tcp:10.10.0.25:2809. Detected GIOP 1.2 protocol 
> error in input message. Connection is closed

It's possible to trigger that message by giving a URI to the name
service that explicitly asks for GIOP 1.2, something like
corbaname::1.2@my.host.name . omniORB 3 only supports GIOP 1.0, so it
replies to the 1.2 message with GIOP 1.0 MessageError message, leading
to omniORB 4's complaint.

As long as you don't specify a GIOP version, or you specify 1.0, it
works fine. How are you configuring the omniORB 4 client?

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --