AW: [omniORB] Java, Python, CORBA
evgeni.rojkov at durr.com
evgeni.rojkov at durr.com
Wed Feb 11 16:40:38 GMT 2009
> Java's orbd doesn't support the interoperable naming service, so you can't use
a corbaname URI to resolve it.
> The Java ORB uses a proprietary bootstrap
> mechanism invented by Sun. Luckily for you, omniORB supports it too. It should
work if you use these arguments instead of the
> -ORBInitRef:
> -ORBInitialHost localhost -ORBInitialPort 900
... just a confirmation...
I could replace omniNames with orbd -ORBInitialPort 2809
It works for omniORB-4.0.5 with Java 1.4
Kind Regards, Evgeni
-----Ursprüngliche Nachricht-----
Von: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] Im Auftrag von Duncan Grisby
Gesendet: Mittwoch, 11. Februar 2009 16:18
An: Jakub Moskal
Cc: OmniORB Support
Betreff: Re: [omniORB] Java, Python, CORBA
On Wednesday 11 February, Jakub Moskal wrote:
> I wrote a server in Java and clients in Java and Python. Clients
> connect and invoke methods without any problem when the object
> reference is retrieved from a string. When I use 'orbd' and
> NameService only the Java client connects, the python clients fails
> with "omniORB.TRANSIENT_ConnectFailed". I init the ORB in python with
> parameters " ["-ORBInitRef", "NameService=corbaname::localhost:900"]
> ". What is the port on which 'orbd' runs its NameService? I tried some
> other ports but all gave me the same error.
Java's orbd doesn't support the interoperable naming service, so you can't use a
corbaname URI to resolve it. The Java ORB uses a proprietary bootstrap mechanism
invented by Sun. Luckily for you, omniORB supports it too. It should work if you
use these arguments instead of the
-ORBInitRef:
-ORBInitialHost localhost -ORBInitialPort 900
> My second question has to do with creating new objects. I wrote an
> object factory on client that returns new objects which implement my
> interfaces, e.g.
Everything you've done looks fine, so I don't know why you'd be getting such a
strange problem. It's definitely nothing to do with the omniORB end, though.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --
_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
More information about the omniORB-list
mailing list