-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FromStringDeserializer
ignores registered DeserializationProblemHandler
for java.util.UUID
#1629
Comments
Thank you for reporting this. It does indeed look like this deserializer does not add (relatively) new handler method, but instead directly calls method to throw exception. This should not happen. |
One question first: which Jackson version? I can not reproduce this with 2.8.8. |
I tested in 2.9.pr3, so most recent version -not sure how far it goes back. |
Hmmh. This is odd, considering test I added passes... I'll try your test case exactly as shown. |
Ah... interesting. This is triggered by returning of |
FromStringDeserializer
ignores registered DeserializationProblemHandler
for java.util.UUID
Fixed; I hope this does not introduce problems with other deserializers -- but if it does, those can be worked around, by not using |
Culprit appears to be lines 155-161 of FromStringDeserializer:
The above lines appear to show that the exception will be thrown regardless of any problem handling logic.
Test Case:
The handler handles the issue properly; but an exception is thrown anyway:
The text was updated successfully, but these errors were encountered: