You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may reduce this problem.
But why we need check this typekey???
You should know this converter may be registered as early as possible.
So if the type changes then converter may not work as expected.
The text was updated successfully, but these errors were encountered:
Orika converter may works like below
So we need equals to support
But we find this
We need check typeKey again ??? Even class is same???
We go on with TypeKey
So we must know the bytes how to computed
Ok we can see getTypeIndex
Sadly
This is not thread safe.
So it may cause key missing in high concurrency.
Even in 1.5.4 Orika change to
It may reduce this problem.
But why we need check this typekey???
You should know this converter may be registered as early as possible.
So if the type changes then converter may not work as expected.
The text was updated successfully, but these errors were encountered: