SDK uses jackson annotation from shaded jar instead of main package

[kartikeytewari-ul]

Describe the bug

The SDK uses jackson for serialisation and deserialisation. The sdk's jackson enforces the user to use annotation from unlogged sdk in there project like selogger.com.fasterxml.jackson.annotation instead of using the annotation from main jackson package like com.fasterxml.jackson.annotation.

This forces the user to modify the code base in few places for the SDK to work properly.

Reproduction steps

Project: unlogged-spring-maven-demo Class: SessionExceptions Pojo: Department and Employee

• Direct invoke SessionExceptions with both pojos having @JsonManagedReference and @JsonBackReference from selogger.com.fasterxml.jackson. In mock created for findAll, hover over the output value. It will be populated correctly with data.
• Modify pojos to use annotations from com.fasterxml.jackson. Mock value will now throw an infinite recursion stack trace, since the SDK did not use the annotation values.

Expected behaviour

The SDK should use the annotation of main jackson package.

[kartikeytewari-ul]

RCA:

• Default implementation of findReferenceType in JacksonAnnotationIntrospector checks if a fields has the annotation of type JsonManagedReference or JsonBackReference. But when that check happens, these class gets resolved to classes inside SDK like selogger.com.fasterxml.jackson.annotation.JsonManagedReference.
• When user also uses selogger.com.fasterxml.jackson, then issue does not comes since the pojo field are indeed annotated with the annotations.
• When user uses just com.fasterxml.jackson them the match fails.

Proposed fix:

1. findReferenceType can be modified to check for both classes inside selogger and in main jackson package.
2. _findAnnotation is the downstream call from all methods including findReferenceType to check presence of annotation. This can be modified to check annotations inside and outside of selogger package.

[kartikeytewari-ul]

This is resolved in PR #110