Re: omniORB 4.3: exceptionIdInAny config parameter

On Thu, 2022-05-19 at 22:45 +0200, [email protected]
wrote:
> please find below a more streamlined test showing the problem,
> directly derived from omniORB's simplest 'echo' example.

Thank you!  That made it very easy to reproduce.

The problem was that the DII user exception code was reusing the Any
unmarshalling code, even though the thrown exception in the marshalled
data from the server was not contained in an Any. The new
exceptionIdInAny parameter caused that to fail. The fix it to not use
that code path, but handle unmarshalling the user exception value into
an Any specifically for the DII case.

It is fixed in the 4_3 branch in SVN and in the latest snapshot
tarball.

Thanks,

Duncan.

-- 
Duncan Grisby <[email protected]>