[omniORB] build problems

[Duncan Grisby]

On Tuesday 12 June, Richard Hardgrave wrote:

> 	I'm trying to convert an Orbix IDL to omniORB. Is this something I
> should even attempt in an incremental fashion, or should I just redesign
> from scratch?  It appears that at least one of the interface methods (e.g.,
> request_es) has an argument mismatch between the base class definition that
> it inherits and its derived class definition. There _are_ definitions for
> all the base class methods in the derived class. I'm just hoping that I just
> don't understand something about the build environment. Or, is this one of
> those parts of the architecture that do not translate from BOA to POA?
[...]

The problem is not really to do with BOA/POA differences, but rather
that the mapping for out arguments has changed. For example, in your
function

	    virtual void request_es (
		const char * sourceGroupName, 
		TosES::E_S_ptr& es);

you should use

	    virtual void request_es (
		const char * sourceGroupName, 
		TosES::E_S_out es);

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --