[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker_development

Title:ObjectBroker Development - BEA Systems' CORBA
Notice:See note 2 for kit locations; note 4 for training
Moderator:RECV::GUMBELd
Created:Thu Dec 27 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2482
Total number of notes:13057

2460.0. "proxy question" by NETRIX::"[email protected]" (Kevin Daly) Wed Mar 26 1997 07:08

Problem Description:

I am trying to write a C++ program that displays both Client and Server
characteristics. This Proxy passes sequences of structures between a 
client and a server.

          Sequence of structs           Sequence of structs
Client    <----------------->  Proxy  <--------------------> Server


In order to build the Proxy I link against server object files 
(Dispatch and Method) and Client objects (Stub). 

I am encountering problems with multiply defined symbols. This is
because the constructor and accessor methods for the sequences and 
structs are appearing in both the client and server object files.

Is there is any easy way to fix this? 

ObjectBroker 2.7.11, DEC C++ 5.5, Digital Unix 3.2

/Kevin. 

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
2460.1SEND::SLAVINWed Mar 26 1997 08:559
>ObjectBroker 2.7.11, DEC C++ 5.5, Digital Unix 3.2

Note, you are using a compiler that is not supported by this release of OBB. 

OBB V2.7-10 and V2.7-11 support DEC C++ V5.0 on Digital Unix.

This is probably not causing your problem, but may cause others in 
the future, as OBB was not tested with the compiler you have selected.
2460.2Use external typecodes if it is both a client and a serverSEND::VLATASWARNING: Do not swallow the battery doorWed Mar 26 1997 09:1312
    
    If your app is both a client and a server, you should generate
    external typecodes. This will generate one typecode module for
    your application instead of generating them in both the client
    stub module and the server side dispatcher module.
    
    Also, for C++ there is a known problem that shows up with a C++
    client/server in some circumstances (PTR 16-3-251) that may
    affect you. The workaround for this problem is to remove the
    INCLUDED_BY_IMH #define in the generated HXX file.
    
    Tony
2460.3OBB and C++ on Digital Unix - versions?NETRIX::&quot;[email protected]&quot;Paul DoyleThu Apr 03 1997 09:3316
> SEND::SLAVIN on Wed, 26 Mar 1997 08:55:11 EST
>
> OBB V2.7-10 and V2.7-11 support DEC C++ V5.0 on Digital Unix.

According to http://www.zk3.dec.com/decc/decc-kitinfo.html, DEC C++ V5.0 
is pre-August 1995 and is no longer available from the internal 
distribution site.

Should I look elsewhere for V5.0, or is anything more recent than V5.0
supported by OBB 2.7-11?

Thanks,

Paul

[Posted by WWW Notes gateway]
2460.4RECV::SLAVINThu Apr 03 1997 10:076
>Should I look elsewhere for V5.0, or is anything more recent than V5.0
>supported by OBB 2.7-11?

The OBB V2.7-11 CLD release was a critical bug fix release for OBB 
V2.7. So we did not alter compilers used. No other compilers were 
tested by the team for that release.
2460.5Re: OBB and C++ on Digital Unix - versions?'NETRIX::&quot;[email protected]&quot;Paul DoyleThu Apr 03 1997 11:3117
RECV::SLAVIN on Thu, 03 Apr 1997 09:07:48 EST said:

> >Should I look elsewhere for V5.0, or is anything more recent than V5.0
> >supported by OBB 2.7-11?
>
> The OBB V2.7-11 CLD release was a critical bug fix release for OBB 
> V2.7. So we did not alter compilers used. No other compilers were 
> tested by the team for that release.

I understand that C++ 5.5 for Digital Unix is the earliest with an STL 
implementation - are we going out on a limb if we use this?

Thanks,

Paul

[Posted by WWW Notes gateway]
2460.6REQUE::BOWERPeter Bower, ObjectBrokerSun Apr 06 1997 19:409
    
> I understand that C++ 5.5 for Digital Unix is the earliest with an STL 
> implementation - are we going out on a limb if we use this?
    
    I doubt you will see any major problems due to the C++ version. I know
    of one warning in the .hxx file concerning a friend declaration;
    this can be worked around by adding a keyword.