Closed MFlisar closed 6 years ago
I'm not a huge fan of ObjectStream serialisation. I am willing to add some serializer without dependencies if you have a good idea for an implementation, but as you have seen in your other issue this is not very robust. JSON for example would also survive changes in fields of classes without runtime error.
I don't have an idea for a more simply serialisation currently, but I understand your concerns and it make sense to me. It's just two functions though, I have them in my local core library I use in all my projects, so I'm fine with this. Was just a suggestion
could you add a default serialiser that does not depend on anything special? No jackson and no gson?
I usually use following in all my projects:
This could be packed into a small extension...