SQS Client Jackson Serialization Conflicting Setter Definitions #5726
-
I have a class that builds SQS Client by reading from YAML configurations, which ran into this issue during our v1 to v2 migration.
Based on what I have collected, this is due to v2 removing external dependency on jackson? Is there a recommended workaround? It seems like I can use Mix-In classes for ObjectMapper to potentially resolve this, but I wonder if there's official guidance on this. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
This is due to v2 removing dependency on Jackson-databind. My solution was implementing custom deserializer on the POJOs. |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
This is due to v2 removing dependency on Jackson-databind.
My solution was implementing custom deserializer on the POJOs.