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
jsonschema2pojo requires only that Jackson can serialize the generated types, not that they must be serializable according to java.io.Serializable. This interface should be removed from generated POJOs.
It's possible to create a schema that causes types to generated that have references to java.lang.Object. It's also possible to reference just about any non-serializable class using the javaType property. When this happens, static code analysis tools like findbugs show warnings (since instances can no longer be guaranteed to be serializable).
After this fix, generated POJOs will no longer implement java.io.Serializable.
Original author: [email protected] (April 18, 2012 22:15:06)
jsonschema2pojo requires only that Jackson can serialize the generated types, not that they must be serializable according to java.io.Serializable. This interface should be removed from generated POJOs.
It's possible to create a schema that causes types to generated that have references to java.lang.Object. It's also possible to reference just about any non-serializable class using the javaType property. When this happens, static code analysis tools like findbugs show warnings (since instances can no longer be guaranteed to be serializable).
After this fix, generated POJOs will no longer implement java.io.Serializable.
Original issue: http://code.google.com/p/jsonschema2pojo/issues/detail?id=45
The text was updated successfully, but these errors were encountered: