[CXF-4227] AttachmentDeserializerTest contains buggy code for reading an InputStream.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.3.10, 2.4.7, 2.5.3, 2.6
• Component/s: WS-* Components
• Labels: patch
• Estimated Complexity: Novice
• Assignee: Freeman Yue Fang
• Reporter: Andreas Krüger
• Created: 04/Apr/12 19:47
• Updated: 23/Apr/12 16:45
• Resolved: 06/Apr/12 09:49

Description

Browsing through the CXF code, I stumbled over the following in AttachmentDeserializerTest, method testCXF3383():

for (int x = 1; x < 50; x++) {
    String cid = "1882f79d-e20a-4b36-a222-7a75518cf395-" + x + "@cxf.apache.org";
    DataSource ds = AttachmentUtil.getAttachmentDataSource(cid, message.getAttachments());
    byte bts[] = new byte[1024];
            
    InputStream ins = ds.getInputStream();
    int count = ins.read(bts, 0, bts.length);
    int sz = ins.read(bts, count, bts.length - count);
    while (sz != -1) {
        sz = ins.read(bts, count, bts.length - count);
    }
    assertEquals(x + 1, count);
}

I think some "count += sz" has been forgotten. Details:

• The while-loop does nothing to change the test result.
• Endless loop, should "ins" ever deliver 1025 bytes or more.
• (If "ins" is 0 bytes, then count will be -1.)
• The fix is obvious, I'll attach a patch.

The problem does not show as long as "ins" contains less than 1024 bytes and all its content is delivered with the first read operation. So no functional impairment, just code hygiene.