-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Undefined
-
Workaround Exists
-
-
-
It's the same issue explained in the upstream yasson project: issue 342 . If a custom deserializer uses the getValue method the level is not updated in the same way that happens when getObject or getArray methods are executed. That method javadoc says:
Returns a JsonValue at the current parser position. If the parser state is START_ARRAY, the behavior is the same as getArray(). If the parser state is START_OBJECT, the behavior is the same as getObject(). For all other cases, if applicable, the JSON value is read and returned.
So it's clear that the getValue method should act exactly in the same way of the other methods in case of an array or an object.
- clones
-
WFLY-14561 Incorrect deserialization using getValue method
- Closed
- is cloned by
-
JBEAP-21213 [GSS](7.3.z) WFLY-14561 - Incorrect deserialization using getValue method
- Closed
- is incorporated by
-
JBEAP-21263 [GSS](7.4.z) Upgrade yasson from 1.0.5 to 1.0.9
- Closed