[omniORB] Problem with omniORB client + Orbix Web server

[Romans Krjukovs]

Hello !

I'm starting using omniORB and i just stopped on such problem:
I have a omniORB client. Code is simple:

  import sys, CosNaming
  from omniORB import CORBA, PortableServer

  orb =3D CORBA.ORB_init()
  obj =3D orb.resolve_initial_references("NameService")
  print "Stringified NameServide obj. reference =3D '" + =
orb.object_to_string(obj)

  rootContext =3D obj._narrow(CosNaming.NamingContext)
  print "Stringified rootCOntext obj. reference =3D '" + =
orb.object_to_string(rootContext)


When ORB is configured to use omniORB Name Service - this code works =
fine.
If i reconfigure to use Orbix Name Service (in registry =
NameService=3Dcorbaname::LETTO:1570) - my code fails.
with Error message:

Traceback (most recent call last):
  File "C:\omniCX2\NS_server.py", line 13, in ?
    rootContext =3D obj._narrow(CosNaming.NamingContext)
  File "C:\omniORB\lib\python\omniORB\CORBA.py", line 650, in _narrow
    return _omnipy.narrow(self, dest._NP_RepositoryId)
omniORB.CORBA.TRANSIENT: Minor: TRANSIENT_NoUsableProfile, COMPLETED_NO.

So, it is about profile. And it is not usable.
I found similar problem description in=20
http://www.omniorb-support.com/pipermail/omniorb-list/2003-May/023556.htm=
l
and Duncan wrote there:
This shows that there was no IIOP profile in the object reference from =
ORBit.

I get a IOR and parse them with =
http://www2.parc.com/istl/projects/ILU/parseIOR/:

omniORB's Name Service IOR parsing:
_IIOP_ParseCDR:  byte order LittleEndian, repository id <>, 1 profile
_IIOP_ParseCDR:  profile 1 is 35 bytes, tag 0 (INTERNET), LittleEndian =
byte order
(iiop.c:parse_IIOP_Profile):  bo=3DLittleEndian, version=3D1.0, =
hostname=3Drkrjukov, port=3D2809, object_key=3D<NameService>
(iiop.c:parse_IIOP_Profile):  encoded object key is <NameService>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is =
<iiop_1_0_1_NameService at tcp_rkrjukov_2809>
object key is <NameService>;
 no trustworthy most-specific-type info; unrecognized ORB;
 reachable with IIOP 1.0 at host "rkrjukov", port 2809

and here is ORBIX Name Service IOR parsing:
_IIOP_ParseCDR:  byte order LittleEndian, repository id <>, 1 profile
_IIOP_ParseCDR:  profile 1 is 31 bytes, tag 0 (INTERNET), LittleEndian =
byte order
(iiop.c:parse_IIOP_Profile):  bo=3DLittleEndian, version=3D1.0, =
hostname=3DLETTO, port=3D1570, object_key=3D<NameService>
(iiop.c:parse_IIOP_Profile):  encoded object key is <NameService>
(iiop.c:parse_IIOP_Profile):  non-native cinfo is =
<iiop_1_0_1_NameService at tcp_LETTO_1570>
object key is <NameService>;
 no trustworthy most-specific-type info; unrecognized ORB;
 reachable with IIOP 1.0 at host "LETTO", port 1570

Both IOR contain 1 profile, both very simmilar (profiles length differ) =
and valid from my point of view.
So, what is the problem with ?

Thanks for Your answers !


BRG,
Romans Krjukovs