[CAMEL-7241] ByteBuffer to String conversion uses buffer capacity not limit

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12.3
• Fix Version/s: 2.11.5, 2.12.4, 2.13.0
• Component/s: camel-core
• Estimated Complexity: Novice
• Assignee: Willem Jiang
• Reporter: Aaron Whiteside
• Created: 25/Feb/14 22:50
• Updated: 28/Feb/14 07:36
• Resolved: 28/Feb/14 07:36

Description

Camel's conversion logic for ByteBuffer's to String's has a bug where camel uses a ByteBuffers capacity() instead of it's limit().

If you allocate a large byte buffer and only partially fill it with data, and use camel to convert this into a string, camel tries to convert all the bytes, even the non-used ones.

This unit test reproduces this bug.

    @Test
    public void testByteBufferToStringConversion()
    {
        String str = "123456789";
        ByteBuffer buffer = ByteBuffer.allocate( 16 );
        buffer.put( str.getBytes() );

        Exchange exchange = new DefaultExchange( context() );
        exchange.getIn().setBody( buffer );
        assertEquals( str, exchange.getIn().getBody( String.class ) );
    }