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
In our project, we plan to generate models of serializable classes in a separate JAR file. For some classes, custom serialization is required, which is located in a separate module where we link interfaces with a specific serializer, as well as connect implementation classes with custom serialization. At the moment, this only works if the class requiring custom serialization does not have the @serializable annotation. However, this variation makes it more difficult to generate a JAR file with the classes, as some classes need to have the annotation while others do not. Is there a way in SerializersModule to replace the default serializer with a custom one?
The text was updated successfully, but these errors were encountered:
See #507 and #2279 (comment). In short, we do not have currently plans for such a feature, as it contradicts framework design. However, it may be implemented in future.
In our project, we plan to generate models of serializable classes in a separate JAR file. For some classes, custom serialization is required, which is located in a separate module where we link interfaces with a specific serializer, as well as connect implementation classes with custom serialization. At the moment, this only works if the class requiring custom serialization does not have the @serializable annotation. However, this variation makes it more difficult to generate a JAR file with the classes, as some classes need to have the annotation while others do not. Is there a way in SerializersModule to replace the default serializer with a custom one?


The text was updated successfully, but these errors were encountered: