harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-2937) [classlib][sql] SerialBlob.truncate(long length) should not change buffer length is the length parameter is invalid.
Date Tue, 02 Jan 2007 16:26:27 GMT

     [ http://issues.apache.org/jira/browse/HARMONY-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim Ellison closed HARMONY-2937.
--------------------------------


Verified by Andrew.


> [classlib][sql] SerialBlob.truncate(long length) should not change buffer length is the
length parameter is invalid.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-2937
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2937
>             Project: Harmony
>          Issue Type: Bug
>          Components: Non-bug differences from RI
>            Reporter: Andrew Zhang
>         Assigned To: Tim Ellison
>         Attachments: patch.diff
>
>
> Hi, as discussed in dev mailing list, SerialBlob.truncate(long length) should not change
buffer length is the length parameter is invalid. Following test shows the case:
> public void testTruncateJ() throws Exception {
>         byte[] buf = { 1, 2, 3, 4, 5, 6, 7, 8 };
>         SerialBlob serialBlob1 = new SerialBlob(buf);
>         try {
>             serialBlob1.truncate(-1);
>         } catch (SerialException e) {
>             System.out.println(e.getMessage());
>         }
>         System.out.println(serialBlob1.length());
> }
> RI output is as follow:
> Invalid arguments: position cannot be less that 1
> -1
> The buffer length is changed to -1 while SerialException is thrown too.  Keeping the
length as the old value makes more sense. Harmony won't follow RI's behaviour for this case,
and keep it as a non-different-bug from RI. 
> Best regards,
> Andrew

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message