RE: Problem when converting IOR to object reference



Hi Frank,

My problems disappeared when I switched from using g_print to printf before the CORBA_ORB_string_to_object call. Don't know why, do you? 

Can you explain why Orbit is warning about the incoming code_sets component when using CORBA_ORB_string_to_object (or ior-decode-2)?

Thanks for your help

/Johan

-----Original Message-----
From: Frank.Rehberger@web.de [mailto:Frank.Rehberger@web.de]
Sent: den 7 januari 2004 00:32
To: Johan Antonsson
Subject: Re: Problem when converting IOR to object reference


Johan Antonsson wrote:

>Hi Frank,
>
>Here you got the IOR and the output from ior-decode-2:
>
>[johan@batman johan]$ ior-decode-2
>IOR:000000000000003e49444c3a73652f666f692f666c65782f6170706c2f6164617074
>6572696e746572666163652f70726f78792f416461707465725365727665723a312e3000
>000000000001000000000000006c000102000000000e3139322e3136382e302e31303000
>0d4400000021afabcb0000000020ec62913d000000010000000000000000000000040000
>00000a000000000000010000000100000020000000000001000100000002050100010001
>0020000101090000000100010100
>
Looks perfectly, and can be decoded by "ior-decode-2", even on your 
machine.  Are you sure this is the output in terminal of client host; or 
did you copy it over from server manually now?  

IDL:omg.org/CORBA/MARSHAL:1.0 normally occures if string has been changed on transfer from server to client, inserting line breaks etc.

Regards, Frank







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]