[omniORB] Possible Empty wstring Unmarshall Bug

[Ken Feuerman]

Now that's service!  Thanks for the quick turn-around!

--Ken Feuerman.
Adobe Systems, Inc.

At 07:18 PM 11/14/2001 +0000, Duncan Grisby wrote:
>On Wednesday 14 November, Ken Feuerman wrote:
>
> > We've discovered that omniORB 4 (snapshot from 12-Nov-2001) is throwing a
> > MARSHALL exception whenever the empty wstring is sent as an IN parameter
> > from the built in ORB with JDK1.4b3.  I've cranked up the omniORB trace
> > level to show the GIOP messages, and it looks like the JDK ORB is
> > marshalling the empty wstring by encoding a 0 length, followed by
> > nothing.  By contrast, it looks like omniORB 4 as a client is marshalling
> > the empty wstring by encoding a length of 2 octets, followed by a BOM
> > (which happens to be 0xfffe in my case).  (Using an omniORB 4 client does
> > NOT cause the servant to throw the MARSHALL exception.)
>
>It's a bug in omniORB. I've fixed it now. I've also changed it so that
>it marshals empty wstrings without a BOM, since it doesn't do any good
>to have it there.
>
>Thanks for the bug report.
>
>Duncan.
>
>--
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --