<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<BASE
href=file://I:\EPOST\marianne-i\Sigs\>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=968022814-08012004>Hi
all,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=968022814-08012004><FONT face=Arial color=#0000ff size=2>Can
someone tell me why I have this unresolved symbol when building my app with
omniORB-4.0.1 on HPUX ?</FONT></SPAN></DIV>
<DIV><SPAN class=968022814-08012004><FONT face=Arial color=#0000ff size=2>or
which omni* lib defines this symbol ?</FONT></SPAN></DIV>
<DIV><SPAN class=968022814-08012004><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2>/usr/lib/dld.sl: Unresolved symbol:
unixTransportDirectory__Q2_4omni13orbParameters (data) from
/main/frlocal/programs/omniORB-4.0.1/hp700-hpux901/lib/libomniORB4.sl.0</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=968022814-08012004><FONT face=Arial color=#0000ff size=2>nm
tells that it is really undef :</FONT></SPAN></DIV>
<DIV><SPAN class=968022814-08012004><FONT face=Arial color=#0000ff size=2>nm
/main/frlocal/programs/omniORB-4.0.1/hp700-hpux901/lib/libomniORB4.sl.0 | grep
unixTransportDirectory | grep
Parameters<BR>unixTransportDirectory__Q2_4omni13orbParameters|
|undef |data |<BR></FONT></SPAN><SPAN class=968022814-08012004><FONT
face=Arial color=#0000ff size=2></DIV></FONT></SPAN>
<DIV><FONT face=Arial><FONT color=#0000ff size=2></FONT><BR><FONT color=#0000ff
size=2></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=968022814-08012004>Thanks
for your help</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2> </DIV>
<DIV><BR></DIV></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
omniorb-list-bounces@omniorb-support.com
[mailto:omniorb-list-bounces@omniorb-support.com] <B>On Behalf Of </B>Rolf C
Stadheim<BR><B>Sent:</B> mercredi 7 janvier 2004 17:33<BR><B>To:</B>
omniorb-list@omniorb-support.com<BR><B>Subject:</B> [omniORB] Is it imperative
to keep client and server interface insync?<BR><BR></FONT></DIV>
<DIV>I was wondering how important it is to keep the stubs and skeletons in
sync,<BR>between client and server?<BR><BR>That is, suppose one have the
following original interface:<BR><BR>mudule test<BR>{<BR>
interface someObj<BR>
{<BR> void
someMethod1();<BR> }<BR>}<BR><BR>The stubs and skeletons for
the client and servant (both C++) are generated,<BR>and all is
well.<BR><BR>Now suppose the interface gets one more method:<BR><BR>mudule
test<BR>{<BR> interface someObj<BR>
{<BR> void
someMethod1();<BR>
void someMethod2();<BR> }<BR>}<BR><BR>and the stubs are
generated, and the client is compiled and linked with<BR>these new stubs. The
servant is unchanged.<BR><BR>Now, if I use this new client, but only call the
original someMethod1() (the<BR>servant naturally does not know anything about
someMethod2()), what are the<BR>consequences, if any?<BR><BR>Access violation,
systems exception, or will this work fine as long as the<BR>client does not
call the new method?<BR><BR>Regards,<BR>Rolf C
Stadheim</DIV></BLOCKQUOTE></BODY></HTML>