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
At the moment, for all model-classes which should be serialized with JSON, exist additional classes.
We have to copy all infos from model-objects to these JSON-objects for serialization and from JSON-objects to model-objects for deserialization .
If the model has a nice design, the JSON-classes are no longer necessary.
There are also some workarounds for the editor in serialization, since it is a OSGi project, the jackson classloader does not see the JSON-classes in the process.util package.
At the moment, for all model-classes which should be serialized with JSON, exist additional classes.
We have to copy all infos from model-objects to these JSON-objects for serialization and from JSON-objects to model-objects for deserialization .
If the model has a nice design, the JSON-classes are no longer necessary.
There are also some workarounds for the editor in serialization, since it is a OSGi project, the jackson classloader does not see the JSON-classes in the process.util package.
https://stackoverflow.com/questions/19724312/jackson-deserializing-custom-classes-in-an-osgi-environment
The text was updated successfully, but these errors were encountered: