JavaIDL and omniORB2

[Ian Brennan]

I've heard that JavaIDL clients can only unmarshal big-endian IIOP
messeages:  They ignore the byte-order member of the GIOP message
header.

That might explain the behaviour you've described below.

Sun don't seem to consider the possibility of Windows servers!

Ian.

-----Original Message-----
From: Henrik Voss <henrik@ifad.dk>
To: omniORB-list <omniorb-list@orl.co.uk>
Date: Thursday, February 12, 1998 4:06 PM
Subject: JavaIDL and omniORB2


>Hi,
>
>I have a (beginners) problem when I use JavaIDL (jdk1.2beta2) with
omniORB2
>(v2.4.0) on WinNT. I am running example 2 from the users manual,
passing the
>object reference as a string via a file from the server to the
client.
>
>The problem arises in the client when the client is written in Java.
I have
>included a few lines of the client below:
>
>  System.out.print("object to string ... ");
>  org.omg.CORBA.Object that = orb.string_to_object(objectString);
>  System.out.println("done");
>
>  System.out.print("narrow object ... ");
>  // Here is the problem!
>  Echo obj = EchoHelper.narrow(that);
>  System.out.println("done");
>
>The problem seem to appear when the generic object reference is
narrowed to an
>Echo proxy object. If the server is running the method invocation is
never
>returning. If the server is not running narrow throws the exception
"unable to
>contact the object.
>
>Any help?
>
>---------------------------------------------------------------
>Henrik Voss, IFAD
>Forskerparken 10, DK-5230 Odense M, Denmark
>Phone: +45 6315 7131, Fax: +45 6593 2999, Email: henrik@ifad.dk
>WWW: http://www.ifad.dk/
>---------------------------------------------------------------
>