[omniORB] OmniORB and JAVAorb, trying to use corbaloc

[Christophe de Vienne]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm answering for my colleague Antoine...

>  You should be able specify the iiop version used like this;
>
> corbaloc:iiop:1.2@myhost.example.com/MyObjectKey
>
> according to OMG corbaloc specification. I do not know, if
> the jdk orb actually implements it.
>

Well, the jdk orb seems to accept this string but if we replace 1.2 by 1.=
0 we=20
get a BAD_PARAM exception on the _narrow...
I'll do some additionnal tests myself ASAP but since it's already the wee=
k-end=20
in France and everybody's gone, I cannot right now. As soon as I have mor=
e=20
things, I'll warn.

Anyway thank you all for your advises (OpenSource Community is really=20
something !).

Best regards,

Christophe


>
> Antoine Thierry wrote:
> > You're good, omniORB is using IIOP 1.0 and JavaORB IIOP 1.2
> > I'd like to force javaorb to use corbalocs with iiop 1.0, but i can't
> > find how to do that ..
> > my corbaloc is
> > corbaloc:iiop:<host_ip>:<host_port>/<object's name on poa>
> > how can i make it iiop 1.0 compliant ?
> >
> > Antoine
> >
> > On Mardi 7 Mai 2002 18:10, Lars Nilsson wrote:
> > > Just out of curiousity, would making sure both omniORB and the Java=
 ORB
> > > uses the same IIOP protocal make any difference? Default IIOP versi=
on
> > > for omniORB3 is 1.0 (I think), while the Java ORB gives you 1.2 (I
> > > think) if you don't specify otherwise.. Perhaps that is causing som=
e
> > > problem.
> > >
> > > Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE82ClXB+sU3TyOQjARArUeAJ0c9wycgFuNkT+6EXDwB7bjLH2vLgCeORAp
or3toQPwOW0u7lJyGlJQx6c=3D
=3D/vMb
-----END PGP SIGNATURE-----