I'm using OpenORB, my question is in the subject.
Thanks
AD
Having that said, it is sometimes useful for administrative purposes
"look inside" an IOR. Usually ORBs come with some command line tools
or such to "dump" an IOR in a "human readable" form. If the IOR is
indeed for an IIOP based server, you should see the hostname/port
somewhere in the output. However, even then you should be aware that
you might not see the hostname/port of your actual server object.
Depending on the ORB implementation you may get the values of some sort
of load balancer, Implementation Repository, etc.
(Try google "openorb iordump").
Anyway, I would not use this information for anything else then
informational purposes.
The CORBA specification does not state how to do that. However, most
CORBA implementations provide a proprietary command-line utility that
will do what you want. These command-line utilities often have names
like "iordump" (Orbix and Orbacus), "catior" (TAO and omniORB) or
"dior" (JacORB). Check your installation of OpenORB to see if it has a
utility with a similar name. If not then the following web site
provides an on-line IOR parser. You just copy-and-paste a stringified
IOR into the form and it will show you the parsed results.
http://www2.parc.com/istl/projects/ILU/parseIOR/
Regards,
Ciaran.
>
> Anyway, I would not use this information for anything else then
> informational purposes.
>
That's what I need it for...
Thanks
AD
If you look into CORBA spec, IOR is represented as a CORBA::struct with
one of the field as ip address and port no.
If you can open a proper byte stream and read the IOR, do required
padding you may read the content of IOR in a proper manner.
And this is what is done by the utility programmes supplied by ORB
vendors to read the content of the IOR.