I used the term "serializer" in the broad sense of "the program which performs the serialization". Yes I'm aware of that, sorry if I was unclear. Is not about what the serializer knows, but the serializer used. You may want to file a bug against spring to handle polymorphic and sealed class serialization in a smarter way (maybe walking the class hierarchy). The valid type to use by spring would be the actual static return type of the function (or other static type of data to be serialized). Especially if that doesn't map to the same dynamic type on deserialization (which it can't). If spring uses dynamic type to determine the serializer it is probably broken. I'm using Spring support for kotlinx serialization, and internally Spring uses serializer() to find the serializer for the object I give to it. The workarounds mentioned here are not possible for me as I don't control the place where Kotlinx.Serialization is called. The child serializer would be (presumably) a leaf serializer. The parent serializer will write out the type discriminator and then delegate writing the actual data to the serializer for the specific type. As such the sealed parent type has a serializer and the child type has a serializer. As such a serializer is specific to each type but also links to subserializer. In this case Json is what we would call the format, when invoking the format it with a serializer parameter (if you use the parameterless versions, you this happens behind the scenes with the inline reified function or dynamically), it will create a corresponding encoder and then asks the serializer to write itself to the encoder. The error .exc.InvalidDefinitionException: Cannot construct instance of .Where you are confused is not about what the serializer knows, but the serializer used. Val response = makeXMLHttpRequest(url,userSerial, HttpMethod.POST, CTX_PRINT_SHOP, "testDeep") The following code still just pushing out the success portion of the sealed class testSealed():TestSealedClass>" Trying it out in a kotlin multi-platform project I was able to remove the dependency on :jackson-module-kotlin:2.10.3 and the project still worked.
0 kommentar(er)
