S3EventNotification deserialization no longer works with AWS SDK v2 S3 Event Notification

[helpermethod]

Type: Bug

Component:
SQS

Describe the bug
S3EventNotification is no longer correctly deserialized when switching from com.amazonaws:aws-java-sdk-s3 to software.amazon.awssdk:s3-event-notifications.

This is due to the following changes: https://aws.amazon.com/de/blogs/developer/the-aws-sdk-for-java-2-17-removes-its-external-dependency-on-jackson/

Because the constructor and fields are no longer annotated with @JsonCreator and @JsonProperty, Jackson is no longer able to map the JSON correctly.

It's easy to work around it by accepting a String instead of a S3EventNotification in the listener and then performing the deserialization by calling S3EventNotification.fromJson but it would be nicer this wouldn't be needed.

@SqsListener("\${sqs.currents.notifications.processed.queueName}")
fun listen(s3EventNotificationJson: String) {
    val s3EventNotification = S3EventNotification.fromJson(s3EventNotificationJson)

    copyService.copy(s3EventNotification.records.first())
}

One solution could be to provide a custom JSON Deserializer for that case. Wouldn't mind creating a PR.

[tomazfernandes]

Hey @helpermethod, thanks for bringing this up, your PR is welcome!

[tomazfernandes]

Just one comment @helpermethod - if I understand the feature correctly, I think the best way to handle this might be having an ArgumentResolver, similar to what we do with AcknowledgmentHandlerMethodArgumentResolver.

Makes sense?

[helpermethod]

Hi @tomazfernandes,

I guess I also need to register the argument resolver in AbstractListenerAnnotationBeanPostProcessor?

Furthermore: Would it make sense to include software.amazon.awssdk:s3-event-notifications as a dependency as S3EventNotification already provides methods for converting from/to JSON?

[tomazfernandes]

Hey @helpermethod, sorry for the delay.

I guess I also need to register the argument resolver in AbstractListenerAnnotationBeanPostProcessor?

In this case let's use the SqsListenerAnnotationBeanPostProcessor instead, since this is a AWS-specific resolver and the Abstract classes should remain AWS agnostic.

Would it make sense to include software.amazon.awssdk:s3-event-notifications as a dependency

I would not add a dependency just to solve this one use case, but I'll defer the dependency management decision to @maciejwalkowiak.

Thanks and please let me know if there's anything else you need.

[maciejwalkowiak]

Can we add it as an optional dependency where if this dependency is present, relevant resolvers get registered?