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

[jiwils - Jimmy Wilson]

I am attempting to get Orbix 3.0.1 and omniORB to interop.  I have managed
to make this happen when the omniORB config file contains the actual IOR for
the Orbix servant.  I would like to get this to work by using the URI method
in the config file.  To do that, I need to extract the object key from the
IOR.

catior.exe outputs the following:

D:\Program Files\omni\bin>catior
IOR:01494f502c00000049444c3a41757468656e7469636
174696f6e5f536572766963652f417574685f536572766963653a312e3000020000000000000
0580
00000010100000800000061637873657233002b064c3a400000003a5c616378736572333a417
5746
85365727665723a303a3a4946523a41757468656e7469636174696f6e5f536572766963655f4
1757
4685f53657276696365000100000018000000010100000100000000000000080000000101000
0305
f5449
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?

Thanks for your help.

Jimmy
-- 
James "Jimmy" Wilson
Software Developer, Acxiom Corporation
E-Mail: jiwils@acxiom.com


-----Original Message-----
From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
Sent: Tuesday, August 01, 2000 11:47 AM
To: jiwils - Jimmy Wilson
Subject: Re: [omniORB] Problems With _narrow(...) When Using A omniORBpy
Client And A Orbix 3.0.1 Servant 


On Tuesday 1 August, jiwils - Jimmy Wilson wrote:

> Would you happen to know of a way to get a servant's IOR without writing
> code to do it?  We've perused the Iona documentation, and there does not
> seem to be one.  So, the only way I know to do it is to call
> object_to_string in client code.  Have I missed something?  This seems to
be
> very problematic to me.

I don't know -- that's a proprietary Orbix thing. Are you using the
automatic process activation facilities of orbixd?  If not, you are
probably better off registering your server in the naming
service. That is a portable solution.

If you do need to stick with using orbixd, I imagine it's possible to
write a little program which binds to any named object and prints its
IOR. Once you've got the program, you could use it for all the
different objects known by orbixd.

Cheers,

Duncan.

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