Replies: 4 comments 9 replies
-
You should be able to configure custom Look at docs here: Let me know if it worked for you! |
Beta Was this translation helpful? Give feedback.
-
Hey @jkatnik, thanks for the feedback! I think we can add About the About the |
Beta Was this translation helpful? Give feedback.
-
Hey @jkatnik, I've created a couple of issues to track the points you brought: I'll get to those soon. In the meantime, do you have any other feedback to provide regarding SQS? Any other issues migrating to 3.0? Thanks. |
Beta Was this translation helpful? Give feedback.
-
@jkatnik, I've created this test and it passes: @Test
void shouldNotSerializeStringPayload() {
String queue = "test-queue";
String payload = """
{ "foo": "bar" }
""";
SqsAsyncClient mockClient = mock(SqsAsyncClient.class);
GetQueueUrlResponse urlResponse = GetQueueUrlResponse.builder().queueUrl(queue).build();
given(mockClient.getQueueUrl(any(GetQueueUrlRequest.class)))
.willReturn(CompletableFuture.completedFuture(urlResponse));
SendMessageResponse response = SendMessageResponse.builder().messageId(UUID.randomUUID().toString()).build();
given(mockClient.sendMessage(any(SendMessageRequest.class)))
.willReturn(CompletableFuture.completedFuture(response));
SqsOperations template = SqsTemplate.newSyncTemplate(mockClient);
template.send(queue, payload);
ArgumentCaptor<SendMessageRequest> captor = ArgumentCaptor.forClass(SendMessageRequest.class);
then(mockClient).should().sendMessage(captor.capture());
SendMessageRequest capturedRequest = captor.getValue();
assertThat(capturedRequest.messageBody()).isEqualTo(payload);
} This tells me |
Beta Was this translation helpful? Give feedback.
-
I'm in the middle of a migration from Spring Boot 2.7 to 3.0.
It forces me to also migrate spring-cloud-aws from 2.4.2 to 2022.0.1
In 2.4
@SqsListener
was utilizing the customMappingJackson2MessageConverter
bean created in our@Configuration
class.In 2022 it looks like
spring-cloud-aws
doesn't search for MappingJackson2MessageConverter in the application context but instead creates its own instance.I went through 3.0.0-RC1 docs but I didn't find any information that this behavior has changed.
Is it a bug or am I doing sth incorrectly?
Beta Was this translation helpful? Give feedback.
All reactions