[omniORB] Problems With _narrow(...) When Using A omniORBpy C lient And A Orbix 3.0.1 Servant

[Duncan Grisby]

On Monday 7 August, jiwils - Jimmy Wilson wrote:

[...]
> Type ID: "IDL:Authentication_Service/Auth_Service:1.0"
> Profiles:
> 1. IIOP 1.0 acxser3 1579
> ":\acxser3:AuthServer:0::IFR:Authentication_Service_Auth_Service."
> 2. Multiple Component Tag
> 
> By using the -x option, the stuff in quotes on line marked 1. changes to
> hex.  Therefore I assume that's the object key.  However when I tried to put
> the stuff in quotes in the config file, the call to ORB_init fails.  Could
> someone tell me if I have the right object key, and what I might need to do
> to make this work?

The problem you're having is that the "." at the end of the key is
actually a null byte, not a "." character. You can see that with
catior -x. It will probably work if you use a % escape to put the null
byte in like:

 ":\acxser3:AuthServer:0::IFR:Authentication_Service_Auth_Service%00"

I'm afraid to say that it might still fail, because some versions of
Orbix don't support the _is_a call which omniORB has to make when
using corbaloc. If that is the case for the version of Orbix you have,
the only option is to use the IOR.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --