[omniORB] DATA_CONVERSION problem with omniORB 4.1.4

[Duncan Grisby]

On Fri, 2012-09-14 at 16:52 -0500, Jingdong Sun wrote:

> IOR string as below: 
> 14 Sep 2012 17:45:38.403 [9509] INFO :::NAM.StartupDaemon
> M[dnameserver.cpp:afterActivation:685]  - DN_NAM Service IOR: 
>    Type ID: IDL:NAM/NameService:1.0 

That's not the IOR string. That's a decoded version of it. It's good
enough though.

[...]
>     Address:  10.6.24.116:48049 
>    Location:  10.6.24.116:48049...SP..%%..... 
>         Key:  fe 82 a5 53 50 00 00 25 25 00 00 00 00 00 

That is not the object reference that the log shows the client
attempting to use. This shows use of an object set with a corbaloc URI:

omniORB: (0) Creating ref to remote: key<dname>
 target id      : IDL:omg.org/CORBA/Object:1.0
 most derived id: 
omniORB: (0) Invoke '_is_a' on remote: key<dname>
omniORB: (0) Client attempt to connect to giop:tcp:d0701b06.pok.hpc-ng.ibm.com:48049

The object reference has object key "dname", not the binary thing shown
above, and the endpoint is identified by name rather than the IP address
that's in your IOR. The corbaloc reference was
corbaloc::d0701b06.pok.hpc-ng.ibm.com:48049/dname

You need a full IOR, including the codeset information, to be able to
send non-ASCII data.

Duncan.

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