Motivation and Context

Similar to #5791 Java SDK v1 uses ByteBuffer to represent binary data while Java SDK v2 uses SdkBytes, so changing the method name is not sufficient for ByteBuffer setters and users will get compilation error.

v1

        MessageAttributeValue messageAttributeValue = new MessageAttributeValue()
            .withBinaryValue(buffer);

to
v2

        MessageAttributeValue messageAttributeValue = MessageAttributeValue.builder()
            .binaryValue(SdkBytes.fromByteBuffer(buffer))
            .build();

Modifications

Convert ByteBuffer to SdkBytes for POJO setters

Testing

Added end to end tests
Unit tests are not possible for JavaTemplate since it can't recognize the types.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license