[omniORB] wstring corruption, omniOrb -> Orbacus

[brk@jenkon.com]

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. Here's a sample of the GIOP (same as for yesterday's
message about a similar problem with OpenOrb):

omniORB: sendChunk: to giop:tcp:209.210.37.31:4121 116 bytes
4749 4f50 0102 0100 6800 0000 0600 0000 GIOP....h.......
0300 0000 0000 0000 2500 0000 abac ab31 ........%......1
3130 3136 3134 3232 3533 005f 526f 6f74 1016142253._Root
504f 4100 00ca feba be3c 9119 ae00 0000 POA......<......
0064 6c2e 0500 0000 6e65 7773 0000 0000 .dl.....news....
0000 0000 0c00 0000 1800 0000 fffe 4800 ..............H.
6500 6c00 6c00 6f00 2000 7400 6800 6500 e.l.l.o. .t.h.e.
7200 6500                               r.e.
omniORB: inputMessage: from giop:tcp:209.210.37.31:4121 28 bytes
4749 4f50 0102 0001 0000 0010 0000 0006 GIOP............
0000 0000 0000 0000 4140 0000           ........A@..

Does anyone know a solution? Is this just a configuration problem of some
kind? Is omniOrb known to work (with wstrings!!) with any Java ORB?

Thanks,

Bryn Keller
Senior Software Engineer
Jenkon
brk@jenkon.com