[omniORB] bug report
Duncan Grisby
dgrisby@uk.research.att.com
Thu, 16 Nov 2000 15:53:13 +0000
On Thursday 16 November, Stefan Seefeld wrote:
> I added the 'try' block to check, and indeed, it is the client which
> catches the BAD_PARAM exception:
>
> 16.9528:0 enter Viewer::press
> omniORB: LocateRequest to remote: root<16777216>
> omniORB: throw BAD_PARAM from giopClient.cc:495
> got a bad parameter !
Yes, that is precisely what is meant to happen. The Python servant
tries to return a bad parameter, so the server-side ORB sends a
BAD_PARAM exception to the client. The client catches it. I don't
understand what you think is wrong.
If you look at line 495 of giopClient.cc, you'll see that that is the
code which unmarshals a system exception sent by the server.
Cheers,
Duncan.
--
-- Duncan Grisby \ Research Engineer --
-- AT&T Laboratories Cambridge --
-- http://www.uk.research.att.com/~dpg1 --