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
This code worked prior to May 6, 2024. However, after our Java runtime was upgraded by Azure, we're now receiving the following error:
Error: Cannot construct instance of com.<company>.data.model.copy.CopyBlobConf (although at least one Creator exists): no String-argument constructor/factory method to deserialize from String value
Is there a security feature that may have been enabled with the March __ release that may have broken Jackson introspection?
Here is the log from our app function that shows the upgrade of the java runtime:
2024-05-07T03:05:51.552Z INFO - Digest: sha256:b57ab4c31547218c65a747fd3762930f07100cf3e939782db4a0b71f0f85dafd
2024-05-07T03:05:51.556Z INFO - Status: Downloaded newer image for mcr.microsoft.com/azure-functions/java:4-java11-appservice-stage3
The text was updated successfully, but these errors were encountered:
Jackson Databind is being used to instantiate a POJO based on a Javascript string, like this:
CopyBlobConf copyBlobConf = Mapper.jsonMapper().readValue(body, CopyBlobConf.class);
This code worked prior to May 6, 2024. However, after our Java runtime was upgraded by Azure, we're now receiving the following error:
Error: Cannot construct instance of
com.<company>.data.model.copy.CopyBlobConf
(although at least one Creator exists): no String-argument constructor/factory method to deserialize from String valueIs there a security feature that may have been enabled with the March __ release that may have broken Jackson introspection?
Here is the log from our app function that shows the upgrade of the java runtime:
2024-05-07T03:05:51.552Z INFO - Digest: sha256:b57ab4c31547218c65a747fd3762930f07100cf3e939782db4a0b71f0f85dafd
2024-05-07T03:05:51.556Z INFO - Status: Downloaded newer image for mcr.microsoft.com/azure-functions/java:4-java11-appservice-stage3
The text was updated successfully, but these errors were encountered: