[omniORB] wstring corruption, omniOrb -> Orbacus

[Duncan Grisby]

On Thursday 14 March, brk@jenkon.com wrote:

> Working with the 12 Mar 2002 omniOrb4 snapshot and the latest Orbacus, if I
> send a wstring from an omniOrb client to an orbacus server, by the time my
> code receives the wstring on the server, it's been transformed to a string
> of question marks.

That sounds like the sort of thing that might happen if ORBacus didn't
understand the codeset that omniORB set. The spec says that if the ORB
can't translate a character into the codeset it is using, it should
throw the DATA_CONVERSION exception, but perhaps ORBacus is replacing
characters with question marks. Of course that doesn't explain why it
doesn't understand the code sets.

Can you send a wstring from ORBacus to omniORB?  What does the omniORB
GIOP trace look like then?  If that doesn't work either, can you get a
trace of ORBacus talking to itself (or OpenOrb talking to itself)?

Cheers,

Duncan.

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