[jacorb-bugs] [Bug 1020] New: Null String encoding is not following strict IIOP

bugzilla-daemon at jacorb.org bugzilla-daemon at jacorb.org
Fri Sep 4 10:57:08 CEST 2015


http://www.jacorb.org/bugzilla/show_bug.cgi?id=1020

            Bug ID: 1020
           Summary: Null String encoding is not following strict IIOP
           Product: JacORB
           Version: 3.5
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ORB
          Assignee: jacorb-bugs at lists.spline.inf.fu-berlin.de
          Reporter: david.shay at externe.bnpparibas.com

When encoding zero length String, Jacorb is creating a String of length one
with the terminating zero character. 
However, when you switch on the null String encoding
(jacorb.interop.null_string_encoding=on), it generates a zero length String,
that can break the server ORB which can not unmarshall it.

in CDROutputStream, encoding of a zero length stream:
if (valueLength == 0)
{
    // Blank string; just write size and terminator. Don't need to
    // align here as these methods will do it for us.
    write_long( 1 );
    write_octet( (byte)0 );
}

null string encoding:
if (nullStringEncoding)
{
    write_long(0);
    return;
}

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-bugs/attachments/20150904/3e051df8/attachment.html>


More information about the jacorb-bugs mailing list