[omniORB] [omniNames]

[Bruno PATIN]

Il s'agit d'un message multivolet au format MIME.
--------------FA9D58E984458C543B1B3BE5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



>   Are you using the proprietary INIT mechanism
> of the SUN Java orb? You have to set
> supportBootstrapAgent=1 in the config file to
> get omniORB4 to support that.

To use this value for supportBootstrapAgent made the interoperability
between omniORB304 an ominORB4. what I can't understand, is that my
client is written in C++ so it's it that use what you name the INIT
mechanism ?? no ?

To go on this track, where can I get information on this INIT mechanism
? how to make the tnameserv equal in behavior with omniORBXXX ? Last, by
default omniNames in 304 version do use this mechanism and not in 4
version ? is that right ? what to do on the client side to avoid this
sort of problems ?

>

and Bjorn, really, thank you very much for your help

ps : perhaps this sort of thing could appear in the FAQ


--------------FA9D58E984458C543B1B3BE5
Content-Type: text/x-vcard; charset=us-ascii;
 name="bruno.patin.vcf"
Content-Description: Carte pour Bruno PATIN
Content-Disposition: attachment;
 filename="bruno.patin.vcf"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by rnis.dassault-aviation.fr id HAA08783

begin:vcard=20
n:patin;bruno
tel;fax:0147115365
tel;work:0147115854
x-mozilla-html:FALSE
url:www.dassault-aviation.fr
org:Dassault Aviation;DPR/ESA
adr:;;78 Quai Marcel Dassault;Saint Cloud;;92552;France
version:2.1
email;internet:bruno.patin@dassault-aviation.fr
title:Ing=E9nieur R&D
fn:bruno patin
end:vcard

--------------FA9D58E984458C543B1B3BE5--