Jackson databind conflicts issue

[bhupendergiri]

Hi,

I am facing an issue which is closed in #30554.

Any suggestion? or advice. Below is the message

java.lang.IllegalAccessException: no such method: com.fasterxml.jackson.databind.cfg.MapperConfig.getAccessorNaming()Provider/invokeVirtual
16:50:01.033 [main] DEBUG c.a.c.i.j.MemberNameConverterImpl - Failed to retrieve MethodHandles used to get naming strategy. Falling back to BeanUtils. Please consider updating your Jackson dependencies to at least version 2.12
16:50:01.027 [main] INFO c.a.c.i.jackson.JacksonVersion - Package versions: jackson-core=2.13.5, jackson-databind=2.13.5, jackson-dataformat-xml=2.13.5, jackson-datatype-jsr310=2.13.5, azure-core=1.34.0, Troubleshooting version conflicts: https://aka.ms/azsdk/java/dependency/troubleshoot

you can also see
com.fasterxml.jackson.databind.cfg.MapperConfig.getAccessorNaming()' the class loader 'bootstrap' of the current class, java/lang/Object, and the class loader org.springframework.boot.loader.LaunchedURLClassLoader @66f5a02e for the method's defining class, com/fasterxml/jackson/databind/cfg/MapperConfig, have different Class objects for the type com/fasterxml/jackson/databind/introspect/AccessorNamingStrategy$Provider used in the signature (java.lang.Object is in module java.base of loader 'bootstrap' com.fasterxml.jackson.databind.cfg.MapperConfig is in unnamed module of loader org.springframework.boot.loader.LaunchedURLClassLoader @66f5a02e, parent loader 'app')

[alzimmermsft]

@bhupendergiri I see you've also filed this issue which I've been working on: #34462

The newer version of the SDK I mentioned in the issue should resolve this issue by changing how these methods are called to reduce the amount of reflection used to handle multi-version support.