AW: [omniORB] can't get rid of omniORB.BAD_PARAM_WrongPythonType

[Daschner, Stefan]

Hi Duncan,

thank you very much.
That was a great help for me.

Is there a possibility to get more information in such a case e.g. which parameter is bad ?

Another question:
I noticed that I get the following errors on server side when the client program (normally) ends:
omniORB: Error in network receive (start of message): giop:tcp:127.0.0.1:27199
omniORB: throw giopStream::CommFailure from giopStream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)

Do I have to do something to avoid this ?

Cheers
Stefan


-----Ursprüngliche Nachricht-----
Von: Duncan Grisby [mailto:duncan at grisby.org] 
Gesendet: Samstag, 31. März 2007 13:26
An: Daschner, Stefan
Cc: omniorb-list at omniorb-support.com
Betreff: Re: [omniORB] can't get rid of omniORB.BAD_PARAM_WrongPythonType 

On Friday 30 March, "Daschner, Stefan" wrote:

[...]
> interface myInterface {
>   long transmit(in any mesg);
> };

[...]
> class myIDL_i (myIDL__POA.myInterface):
>     def transmit(self, myInStruct):
>         print "the received object: \n", myInStruct

You haven't returned a value, meaning that transmit() returns None. The
IDL says it must return a long. If you return a value, you'll find you
no longer get the exception.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --